Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ads_list_accessible_customers

Read-onlyIdempotent

Lists Google Ads customer resource names accessible to the authenticated user, enabling selection of the right account for ad queries and operations.

Instructions

List Google Ads customer resource names directly accessible to the authenticated user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_list_accessible_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description contributes one genuinely useful trait beyond that: only *directly* accessible customers are returned, implying manager-hierarchy or indirect accounts are excluded. It adds nothing about authentication requirements, pagination, or result shape, which is acceptable for a flat list but leaves the behavioral picture thin.

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?

One sentence, front-loaded with the verb and resource, with no filler or redundancy. Every clause ('directly accessible', 'authenticated user') carries scope information that constrains the result.

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?

For a zero-parameter read-only list with full annotation coverage and no output schema, the definition is nearly sufficient: it conveys the resource type and the access scope. The remaining gap is that it does not state the return value format (resource-name strings) or that these names feed other Ads calls, which would have made it self-contained.

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

Parameters4/5

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

The tool takes no parameters and the schema is empty with additionalProperties=false, so there is no parameter meaning to explain. Baseline of 4 applies; the description correctly implies the entire result set is determined by the caller's credentials rather than any input.

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?

The description uses a specific verb ('List') and a precise resource ('Google Ads customer resource names') with an explicit scope ('directly accessible to the authenticated user'). This clearly separates it from siblings such as ga4_list_account_summaries or the gtm_list_* family, which target different products and entity types. It stops short of a 5 because it never states the practical outcome (obtaining customer IDs to pass to other Ads tools).

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?

Usage is only implied: a zero-parameter list of accessible resources reads as a discovery/entry-point call, but the description never says to call it before other Ads tools or when to prefer it over them. No exclusions, prerequisites, or alternative routes are named, so the agent must infer placement in a workflow.

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