Retrieve detailed information for a specific Google Ads customer account by entering its customer ID. Access account-level data for analysis and campaign planning.
Get detailed information for a specific Google Ads customer account.
| Name | Required | Description | Default |
|---|---|---|---|
| customerId | Yes | Google Ads customer ID (without dashes, e.g., 1234567890) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'Get' implies a read-only operation, which is useful, but the description does not specify what 'detailed information' includes, whether special permissions are needed, or how errors are returned.
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 one concise sentence with no filler or repetition. It is front-loaded with the action and clearly names the target resource, making it easy for an agent to parse quickly.
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 one-parameter read tool the description is functional, but there is no output schema and the description does not specify what details are returned. This leaves or some ambiguity about the tool's output, though the basic invocation requirements are fully covered.
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 input schema covers 100% of parameter documentation, including the customerId format example ('without dashes'). The description adds no additional parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.
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 clear verb and resource: 'Get detailed information for a specific Google Ads customer account.' It distinguishes itself from list-oriented siblings like google_ads_list_accounts by emphasizing a specific account, though it does not explicitly name alternatives or contrast with google_ads_get_account_hierarchy.
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 phrase 'for a specific Google Ads customer account' implies this should be used when the caller already has a customerId and needs account-level details. However, there is no explicit guidance about when to choose this tool over sibling tools or any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.