Skip to main content
Glama
kLOsk

Google Ads - AdLoop

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Google Ads accounts

list_accounts
Read-only

Enumerate accessible Google Ads accounts to view names, IDs, and status. Supports high-volume account lists with configurable limits.

Instructions

List accessible Google Ads accounts.

Returns account names, IDs, and status. The default cap of 200 covers the vast majority of agency MCCs in one call. If the user explicitly asked to see ALL of their accounts and the response comes back with 'truncated: true', call this tool again with a much higher limit (e.g. list_accounts(limit=1000)) — do not stop at the truncated list. For workflows that target a specific account you don't need to enumerate at all: pass customer_id directly to get_campaign_performance, run_gaql, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.6/5.0
Behavior4/5

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

The description mentions the default cap and the 'truncated' behavior, adding useful context beyond the read-only annotation. It does not contradict the annotations and provides enough transparency for a read-only list operation.

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?

The description is succinct, with no redundant phrasing. It front-loads the main purpose and includes only essential guidance about limit and alternative usage. Every sentence serves a purpose.

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?

Covers the key aspects: what is returned (names, IDs, status), the default cap, and handling of truncation. While it does not enumerate output schema details, the tool's purpose is fully explained for an agent to decide and call it correctly.

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?

Only one parameter, 'limit', is present. The schema provides type and default, but the description explains its purpose (controlling the number of accounts returned) and how to adjust it in response to truncation. This compensates for the lack of schema description.

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?

The description clearly states the tool lists accessible Google Ads accounts, distinguishing it from sibling tools like list_merchant_accounts and list_gsc_sites. The verb 'list' is specific and the resource is unambiguous.

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

Usage Guidelines5/5

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

Explicitly provides guidance on when to increase the limit (if results are truncated when user asks for all accounts) and when not to use this tool (when targeting a specific account, pass customer_id directly to other tools). This directly informs tool selection.

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

Deploy Server

Other Tools