Skip to main content
Glama

List keywords

list_keywords
Read-only

List keywords across visible campaigns. Pass ad_group_id or campaign_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_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return. Default 50, max 200.
cursorNoOpaque pagination cursor returned by the previous page in meta.nextCursor.
platformNoOnly return keywords on this platform (their ad group's). Each keyword 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 keywords in this ad group (server-side scope).
campaign_idNoOnly return keywords 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 keywords on this platform (their ad group's). Each keyword 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=true, but the description adds genuinely new behavior: an unscoped query returns the entire Space and can overflow the response budget. It also discloses that space scoping comes from session binding and can be overridden per call. It stops short of describing ordering or result shape, but no output schema exists so that is a modest gap.

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 compact sentences, each carrying distinct information: what it lists, how to scope it and why, and how Space context is resolved. The recommendation is front-loaded ahead of the override detail, with no redundancy against 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 six-parameter, no-required, read-only list tool with full schema descriptions, the definition covers the decision points an agent needs: scoping, response-size risk, and Space resolution. Nothing critical is missing, though it does not mention pagination behavior (cursor/nextCursor) or default result ordering even in passing.

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 would be 3; the description earns above that by explaining why to use ad_group_id/campaign_id (response-size protection) rather than merely restating their server-side scope. The space_id override is framed in terms of session binding versus one-call override, adding decision-relevant meaning beyond the schema text.

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 keywords") plus a concrete scope ("across visible campaigns"), so an agent knows exactly what collection is returned. The follow-up sentence clarifies that the default unscoped call spans the whole Space, which sharpens the sense of what the tool actually returns.

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?

Gives explicit operational guidance: pass ad_group_id or campaign_id to scope server-side, with a stated recommended default and the consequence of omitting it. It also names the alternative for changing context (set_active_space) and the per-call override (space_id), covering when-to-use-this versus when-to-adjust-context.

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