Retrieve accessible GMP organizations in a single page (up to 1,000) to discover accounts for Admin, DV360, CM360, or SA360—not Google Cloud organizations.
List accessible GMP organizations (one page, max 1000); not Google Cloud organizations.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| page_size | No | ||
| page_token | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral information — results come back as a single page capped at 1000 — which tells the agent to expect truncation and paging rather than a complete listing.
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?
A single front-loaded sentence that states the resource, the scope, the pagination limit, and the disambiguation. Nothing is padded and nothing is buried.
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 explained, and the page cap is a valuable addition. Still, for a 0%-coverage schema the description does not say what 'account' scopes or how page_token is used, leaving real gaps for a paged list tool.
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% and none of the three parameters are documented in the schema. The description's 'one page, max 1000' implicitly caps page_size, but the 'account' parameter and the page_token continuation mechanism are left entirely unexplained.
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 names a specific verb and resource ('List accessible GMP organizations') and scopes it to accessible entities, which is more precise than a bare restatement. It also pre-empts a likely confusion by excluding Google Cloud organizations, though it does not differentiate from the sibling get_organization.
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 word 'accessible' implies this is the entry point for enumerating orgs you can see, and the Google Cloud exclusion usefully rules out a false match. However, there is no explicit guidance on when to call this versus get_organization or list_analytics_account_links, and no prerequisites are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.