ads-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| META_APP_ID | No | Meta App ID | |
| META_APP_SECRET | No | Meta App Secret | |
| ADS_MCP_ENV_FILE | No | Path to an existing .env file containing all credentials | |
| META_ACCESS_TOKEN | No | Meta Access Token (long-lived, with ads_read) | |
| META_AD_ACCOUNT_ID | No | Meta Ad Account ID (format: act_XXXXXXXXX) | |
| GOOGLE_ADS_CLIENT_ID | No | Google Ads Client ID | |
| GOOGLE_ADS_CUSTOMER_IDS | No | Comma-separated customer IDs (no dashes) | |
| GOOGLE_ADS_CLIENT_SECRET | No | Google Ads Client Secret | |
| GOOGLE_ADS_REFRESH_TOKEN | No | Google Ads Refresh Token | |
| GOOGLE_ADS_DEVELOPER_TOKEN | No | Google Ads Developer Token | |
| GOOGLE_ADS_LOGIN_CUSTOMER_ID | No | MCC manager account ID (no dashes) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_google_ads_reportA | Pull Google Ads performance. Returns account totals, campaign-type breakdown, top-50 per-ad rows with diagnosis, 56-day daily series, and WoW + 8-week DoW comparisons. Set include_campaign_settings=True to also return per-campaign settings (target CPA, daily budget, diagnosis, utilization) for ENABLED campaigns only. |
| get_meta_ads_reportB | Pull Meta Ads performance. Same shape as get_google_ads_report. Conversions filtered to META_CONVERSION_EVENT_NAME. |
| get_campaign_settingsC | Current campaign settings + 56-day change history per platform. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct area: campaign settings, Google Ads performance, and Meta Ads performance. No overlap; descriptions clearly differentiate them.
All tool names follow a consistent 'get_' prefix with the specific resource (campaign_settings, google_ads_report, meta_ads_report). Consistent snake_case pattern.
Three tools is minimal but appropriate for a focused ads reporting and settings retrieval server. Could be expanded but current count is reasonable for the stated purpose.
Only read operations are exposed; no create, update, or delete tools for campaigns or ads. Significant gaps for a full ads management workflow.