Google Ad Manager MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GAM_NETWORK_CODE | No | Optional Google Ad Manager network code. If omitted, run list_networks and pass the code per call. | |
| GAM_OAUTH_CLIENT_ID | Yes | OAuth 2.0 Desktop app client ID for Google Ad Manager API authentication. | |
| GAM_OAUTH_CLIENT_SECRET | Yes | OAuth 2.0 Desktop app client secret for Google Ad Manager API authentication. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_networksA | List the Google Ad Manager networks this account can access, with their network codes. Use this to discover the network code if it has not been configured. |
| list_reportsA | List saved reports in Ad Manager. Returns each report's resource name, which is what run_report takes. Use this first to find the report to run. |
| run_reportA | Run a saved Ad Manager report and return its rows. Takes the report resource name from list_reports (e.g. 'networks/12345678/reports/42'). Reporting is asynchronous in Ad Manager; this waits for completion. Read-only — it runs an existing report definition and never modifies it. |
| list_ordersB | List Ad Manager orders, for context alongside report data. Supports a filter expression. |
| list_line_itemsB | List Ad Manager line items, for context alongside report data. Supports a filter expression. |
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 5 tools
Each tool targets a distinct resource and action: list_networks, list_reports, run_report, list_orders, and list_line_items have no overlapping purpose. The descriptions explicitly cross-reference each other (list_reports -> run_report, list_networks for network code), making selection unambiguous.
All tools follow a clean verb_noun snake_case pattern (list_networks, list_reports, run_report, list_orders, list_line_items). No deviations or mixed conventions.
Five tools is a reasonable, focused set for a reporting/listing workflow, though it leans slightly thin for a platform as broad as Ad Manager. Each tool clearly earns its place with no redundancy.
The surface is entirely read-only: it can list networks, reports, orders, and line items and run reports, but has no get-single-item, create, update, or delete operations for any resource. For an Ad Manager management domain this leaves major gaps (order/line item lifecycle, creatives, inventory) that would cause agent dead ends.