Skip to main content
Glama

list_google_ads_accounts

List all Google Ads accounts (and MCC manager status) accessible by the connected Google OAuth token.

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": "list_google_ads_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the auth dependency (requires a connected Google OAuth token) and that results include MCC manager status. It omits other behavior an agent would want: read-only/non-mutating nature, what happens when no token is connected, pagination or result-size limits, and whether empty results are possible.

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?

A single, front-loaded sentence with the verb and resource first and the auth qualifier last. No filler, no redundancy, nothing that could be cut without losing information.

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 tool with no output schema, the description covers the essentials: what is listed, the auth context, and the notable extra field (MCC manager status). It falls slightly short of fully complete because it doesn't hint at the shape of returned identifiers that downstream Google Ads tools presumably need, nor the failure mode when no token is connected.

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 input schema has zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly gives no parameter guidance rather than inventing any.

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?

States a specific verb (List) and resource (Google Ads accounts) plus an extra returned attribute (MCC manager status) and the auth scope (connected Google OAuth token). The resource name alone distinguishes it from siblings like list_microsoft_ads_campaigns and get_google_campaign_report, but the description never explicitly routes the agent versus those tools, keeping it below a 5.

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: an agent can infer this is a discovery/enumeration call to run before account-scoped Google Ads operations, and the phrase 'accessible by the connected Google OAuth token' signals an auth precondition. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., call this before publish_campaign_to_google_ads).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources