List every Google Ads account available through the authenticated credentials. Enables you to identify which accounts you can manage and report on.
List all Google Ads accounts accessible via current credentials.
Returns accounts accessible through the authenticated MCC or direct account.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description adds useful auth-related context: results depend on the authenticated MCC or direct account. This goes beyond the structured annotations without contradicting them.
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 two short sentences with the action and scope front-loaded, followed by a clarifying statement about authentication context. There is no filler or redundant repetition of schema information.
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?
For a simple zero-parameter, read-only listing tool with no output schema, the description tells the agent exactly what it returns and under which credential context. Nothing essential is missing given the low complexity.
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?
The tool has zero parameters and the schema coverage is 100% with an empty properties object. The description appropriately avoids parameter discussion, and the baseline for a zero-parameter tool is satisfied.
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 uses a specific verb ('List') and a clear resource ('all Google Ads accounts accessible via current credentials'). It distinguishes itself from sibling tools like get_account_hierarchy and get_account_info by focusing on enumeration of accessible accounts rather than hierarchy structure or single-account details.
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 description clearly indicates when to use the tool: to enumerate accounts available through the current authenticated credentials, whether via an MCC or direct account. It does not explicitly name alternatives or exclusions, but the context is unambiguous for a zero-parameter listing tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.