AdsAgent — Google Ads MCP

google_ads_insights_query_daily

Read-only

Bounded daily spend for one enabled non-manager customer (ledger by default, narrow default window). Manager/closed/canceled accounts return a skip reason instead of metrics.

Input Schema

TableJSON Schema

Name	Required	Description
`source`	No	Read source; defaults to synced data ('ledger'). 'live' sweeps the API.
`date_to`	No	ISO date (YYYY-MM-DD). Optional.
`date_from`	No	ISO date (YYYY-MM-DD). Optional; defaults to a narrow recent window.
`customer_id`	Yes	10-digit Google Ads customer id.
`connection_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / source / description

Previous value: -"Read source; defaults to the Supabase ledger. 'live' sweeps the API."New value: +"Read source; defaults to synced data ('ledger'). 'live' sweeps the API."

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
First observedSep 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover readOnly/no-destructive/closed-world, so the description's real value is the skip-reason behavior for manager/closed/canceled accounts and the ledger-vs-live source default. It doesn't describe pagination or the output shape (no output schema), leaving gaps despite annotations.

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?

Two tight sentences front-loading scope (bounded daily spend, one customer) then the edge-case behavior. No wasted words.

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

Completeness4/5

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

Covers the edge cases an agent most needs (ineligible accounts skip rather than error) and the source default. Missing output/pagination detail, but for a read-only query tool with rich schema this is close to sufficient.

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

Parameters3/5

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

Schema coverage is 80% with self-documenting params (source enum, ISO dates, customer id pattern). The description reinforces the ledger default and narrow window but adds little syntax or meaning beyond the schema; baseline 3 holds.

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

Purpose4/5

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

States a specific verb (query) and resource (daily spend for one customer) with scope qualifiers (enabled non-manager, ledger by default, narrow default window). Distinguishable from insights_overview_query/batch siblings, though it doesn't name those alternatives explicitly.

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

Usage Guidelines3/5

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

Implies usage context (one enabled non-manager customer, narrow window) but never states when to choose this over google_ads_insights_overview_query or insights_overview_batch. Exclusions for manager/closed/canceled are described as outcomes, not routing guidance.

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

All AdsAgent — Google Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?