Skip to main content
Glama

manage_keyword_list

Destructive

Create, rename, add keywords to, remove keywords from, or delete a client's saved keyword list. A keyword added from a stored lookup (resultKey) keeps that lookup's figures with their dates; one typed in has none until researched. A client has up to 50 lists of up to 5,000 keywords. Delete removes the list only, never a stored lookup. Spends nothing. Requires MCP write actions; without confirm:true it returns a preview.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "clientId": "<clientId>"
    },
    "name": "manage_keyword_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate, rename.
actionYes
listIdNoThe list (rename, add, remove, delete).
confirmNoSet true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
countryNocreate: ISO 3166-1 alpha-2.
clientIdYesClient id (from list_clients).
keywordsNocreate, add, remove.
languageNocreate: language code.
resultKeyNocreate, add: the stored lookup whose figures the added keywords keep.
previewTokenNoWith confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Although annotations already flag destructiveHint=true, the description sharpens what is actually destroyed: 'Delete removes the list only, never a stored lookup', which is exactly the scope detail annotations cannot convey. It also states capacity limits (50 lists, 5,000 keywords) and that operations are free of charge.

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?

Five short sentences, front-loaded with the action set, then the non-obvious semantics (resultKey, delete scope), then constraints and the preview gate. Nothing is redundant with the schema beyond necessary framing.

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 10-parameter mutation tool with no output schema, the description covers action scope, destruction scope, capacity limits, cost and the preview/confirm flow. Minor gaps remain around what the preview returns and which fields each action requires, but the essentials are present.

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 90%, so a baseline of 3 applies, but the description adds real meaning beyond the schema by explaining resultKey behavior: keywords added from a stored lookup keep figures and dates, while typed keywords have none until researched. It also ties action semantics to name, listId and keywords.

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 specific verbs (create, rename, add, remove, delete) applied to a clearly bounded resource: a client's saved keyword list. This distinguishes it from research_keywords and add_rank_keywords, which operate on different resources, though no sibling is named explicitly.

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 clarifies the operational context: 'Requires MCP write actions' and 'without confirm:true it returns a preview', which tells the agent how the call is gated. 'Spends nothing' usefully contrasts with credit-consuming tools like research_keywords, but no explicit when-to-use-this-vs-alternative routing is given.

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