Skip to main content
Glama

List ad groups

list_ad_groups
Read-only

List ad groups across visible campaigns, or in one campaign with campaign_id. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return. Default 50, max 200.
cursorNoOpaque pagination cursor returned by the previous page in meta.nextCursor.
platformNoOnly return the ad groups on this platform (a platform id such as google-ads).
space_idNoOverride the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.
campaign_idNoOnly return the ad groups of this campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Only return the ad groups on this platform (a platform id such as google-ads).",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / campaign_id
      Added value: +{
      +  "description": "Only return the ad groups of this campaign.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context beyond that: results are bounded by the active Space session binding, and space_id is a per-call override that does not mutate the session. It says nothing about ordering or default page size, but those live in the schema.

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, no filler. The primary capability and its scope lead, and the Space/session caveat follows as the secondary concern. Nothing is repeated verbatim from the schema.

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-required-parameter read-only list tool with fully documented parameters and annotations, this covers what an agent needs to call it correctly, including the Space scoping trap. The only gap is the absence of any hint about return shape or paging behavior, which matters slightly more here because no output schema exists.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, cursor, platform, space_id, and campaign_id are all documented in structured fields, which sets the baseline at 3. The description restates the campaign_id filtering behavior and the one-call nature of space_id but adds no syntax, default, or interaction detail the schema lacks.

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 names a specific verb (list) and resource (ad groups) and immediately states the two possible scopes: across visible campaigns, or narrowed to one campaign via campaign_id. That scope language distinguishes it from single-item siblings like get_ad_group and from adjacent list tools such as list_ads or list_campaigns.

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

Usage Guidelines4/5

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

It explicitly tells the agent to pass campaign_id when it wants one campaign's ad groups, and names set_active_space as the way to change the session-wide Space. It does not state when *not* to use it (e.g., use get_ad_group for a single ad group by id), so it falls short of the explicit exclusions a 5 requires.

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