Skip to main content
Glama

List ads

list_ads
Read-only

List ads across visible campaigns. Pass campaign_id or ad_group_id to scope the result server-side (recommended — otherwise the whole Space is returned and can overflow the response budget). 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_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return. Default 50, max 200.
cursorNoOpaque pagination cursor returned by the previous page in meta.nextCursor.
platformNoOnly return ads on this platform (their ad group's). Each ad carries platform.
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.
ad_group_idNoOnly return ads in this ad group (server-side scope).
campaign_idNoOnly return ads in this campaign (server-side scope).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Only return ads on this platform (their ad group's). Each ad carries platform.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, so safety is covered; the description adds genuinely non-obvious behavior: unscoped calls return the whole Space and can blow the response budget, and scope is applied server-side. It does not mention ordering or what fields an ad carries, which keeps it short of a 5.

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?

Three sentences, no filler, with the scoping recommendation placed before the Space-context detail so the most actionable guidance lands first. Every clause carries a distinct instruction.

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 read-only list tool with six optional parameters and no output schema, the definition covers scoping, budget risk, and context switching well. Minor gap: it never characterizes the returned items or ordering, though pagination is fully handled by the cursor parameter description.

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?

Schema coverage is 100%, so the baseline is 3; the description earns one more by explaining the rationale behind campaign_id/ad_group_id (server-side scoping to avoid oversized responses) rather than restating them. The space_id override semantics largely duplicate the schema text but the recommendation adds decision-relevant meaning.

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?

States a specific verb and resource ('List ads') plus the collection boundary ('across visible campaigns'), which tells an agent exactly what population is returned. The Space scoping sentence further pins down the data boundary, so it is distinguishable from competitor-ad or asset listings without opening a schema.

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 recommends the scoping parameters ('Pass campaign_id or ad_group_id... recommended') and states the consequence of not doing so (whole Space returned, response budget overflow). It also names the alternative route for changing Space context ('see set_active_space') and the per-call override, leaving nothing to inference.

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