Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_list_accounts

Read-only

List every Google Ads account your Google login can access, including IDs, names, currencies, manager status, and client accounts under managers.

Instructions

List Google Ads accounts this Google login can access (IDs, names, currency, whether each is a manager), including client accounts under managers.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

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 and openWorldHint=true, and the description is consistent with both, so the safety profile needs no further work. Beyond that it adds the useful detail that manager accounts expose their client accounts, but says nothing about pagination, ordering, or what happens when the login has no accounts.

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 resource and access scope first and the return fields in parentheses. No filler, no repetition of the tool name, nothing that could be cut.

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?

With no parameters, no output schema and permissive read-only annotations, the description carries most of the burden and does describe what comes back, including the manager/client hierarchy. The remaining gap is that it does not connect the returned account IDs to the downstream ads_* tools that require them.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical instead documents the shape of the result, which is the only variable an agent needs to reason about here.

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 and resource ('List Google Ads accounts') and narrows scope to accounts 'this Google login can access', plus it enumerates the returned fields (IDs, names, currency, manager flag). It clearly reads as an account-discovery tool distinct from the performance/query siblings, though it never names an alternative explicitly.

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 the entry point for enumerating accessible accounts before calling the ads_* performance or query tools, but the description never states that ordering or says when not to use it. The note about client accounts under managers gives useful context on what will be returned rather than when to call it.

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