Skip to main content
Glama
ceotind

Google Ads MCP Reader

by ceotind

search

Execute read-only GAQL queries to retrieve Google Ads data like campaigns, ad groups, and performance metrics. Supports manager accounts with automatic child routing.

Instructions

Execute a read-only GAQL query and return flattened results. Workflow: list_accessible_customers() → get_resource_metadata(resource) → search()

If customer_id is a manager (MCC) account, this auto-routes to child accounts and annotates results with _source_customer_id and _source_customer_name — no manual child enumeration needed.

Field rules:

  • Use fully-qualified names: campaign.id (not id), metrics.clicks, segments.date

  • Dates: YYYY-MM-DD format with dashes

  • Relative ranges: DURING LAST_7_DAYS, LAST_30_DAYS, THIS_MONTH, THIS_QUARTER

  • Conditions are AND-combined

  • Ordering: 'field_name DIRECTION' (e.g. 'metrics.clicks DESC')

  • For change_event resource, limit max is 10000

Common conditions: campaign.status = 'ENABLED' campaign.advertising_channel_type = 'SEARCH' segments.date DURING LAST_30_DAYS metrics.impressions > 1000

Example — active campaigns with performance: customer_id='1234567890', resource='campaign', fields=['campaign.id', 'campaign.name', 'campaign.status', 'metrics.clicks', 'metrics.impressions', 'metrics.cost_micros'], conditions=["campaign.status = 'ENABLED'", 'segments.date DURING LAST_7_DAYS'], orderings=['metrics.clicks DESC'], limit=10

Args: customer_id: Numeric Google Ads customer ID (e.g. '1234567890'). Manager (MCC) accounts are auto-detected and routed. resource: GAQL resource name (e.g. 'campaign', 'ad_group', 'keyword_view'). fields: Fully-qualified field names to SELECT. conditions: WHERE clauses joined with AND (optional). orderings: ORDER BY clauses (optional). limit: Max results (default: 100, max varies by resource).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
fieldsYes
resourceYes
orderingsNo
conditionsNo
customer_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and does an excellent job. It declares read-only nature, auto-routing for manager accounts, annotation of results with source fields, field formatting rules (e.g., fully-qualified names, date formats), and behavior for conditions, ordering, and limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured into sections: summary, workflow, field rules, common conditions, example, and Args. Every sentence is informative and there is no redundancy. It is detailed yet concise, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no annotations, but output schema exists), the description covers all essential aspects: purpose, parameters, behavior, edge cases (MCC routing), examples, and field rules. It is comprehensive and leaves no important gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds detailed meaning for each parameter in the Args section: customer_id as numeric with MCC auto-detection, resource name, fully-qualified fields, AND-combined conditions, ordering format, and limit defaults. This fully compensates for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool executes a read-only GAQL query and returns flattened results. It distinguishes itself from sibling tools like get_resource_metadata and list_accessible_customers by focusing on query execution, with a specific workflow mentioned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a workflow (list_accessible_customers() → get_resource_metadata(resource) → search()) that implies when to use this tool. It also provides context about manager account routing and field rules. However, it does not explicitly state when not to use it or compare directly with siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ceotind/open-google-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server