ads.gaql.queryRun read-only GAQL queries against a specified Google Ads customer account to retrieve campaign, ad group, and performance data without changing account settings.
Run an arbitrary read-only GAQL query.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| customer_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is read-only, but it says nothing about authentication, permissions, query limits, rate limits, pagination, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted wording. It is concise, though its brevity leaves important operational details unstated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described. However, for a raw query execution tool with two undocumented parameters and no annotations, the description is too thin to tell an agent how to call it correctly or what constraints apply.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so both parameters need explanation here. The description implies that `query` is GAQL, but it does not explain the GAQL syntax or the meaning and format of `customer_id`.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it runs an arbitrary read-only GAQL query. That is clear enough for an agent to understand the core action, but it does not distinguish this tool from sibling reporting tools such as ads.report.campaign.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only usage signal is that the query is read-only. The description does not explain when to choose this arbitrary GAQL tool over structured siblings like ads.report.campaign, ads.report.search_terms, or ads.change_history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.