Google Ads MCP Unofficial

by davidmosiah

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Accessible Customer Accounts

google_ads_list_accounts

Read-onlyIdempotent

List all Google Ads accounts you can access, including child accounts for manager (MCC) accounts.

Instructions

List all customer accounts the authenticated user can access. For a manager (MCC) account, this includes every child customer.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`response_format`	No		markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`count`	No
`error`	No
`records`	No
`has_more`	No
`privacy_mode`	No
`next_page_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Jul 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent. Description adds clarity on manager account behavior (includes child accounts). No contradictions, good addition.

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?

Two sentences with no fluff; front-loaded with main action. Every word adds value.

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?

Simple tool with output schema; description covers core functionality. Missing parameter info, but overall sufficient for selection.

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

Parameters2/5

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

Only parameter (response_format) is not mentioned in description. With 0% schema coverage, description should explain the enum/default, but it doesn't.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'list' and resource 'customer accounts', distinguishing scope (all accessible, including children for MCC). Differentiates from siblings like google_ads_get_account_performance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like google_ads_get_account_performance or google_ads_list_campaigns. Missing context for selection.

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

Deploy Server