Skip to main content
Glama

list_keyword_research

Read-only

A client's stored keyword lookups (each kept 30 days for the workspace; showing one again is free) and saved keyword lists: seed, type, country, language, keyword count and dates for each lookup; name, country, language, keyword count and last change for each list. Reads only; get_keyword_research opens one.

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": {
      "clientId": "<clientId>"
    },
    "name": "list_keyword_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient id (from list_clients).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds context beyond the annotations: lookups are kept 30 days per workspace, re-showing one is free (no credit consumption), and the tool is read-only. Annotations already declare readOnlyHint/openWorldHint=false, so the added retention and cost semantics are genuine value. Return format detail is thin but the field list compensates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence front-loads the resource and its retention/cost note, then the returned fields, then the read-only and sibling routing. Dense but every clause carries information; the parenthetical cost note slightly interrupts flow but earns its place.

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 one-parameter read tool with annotations and no output schema, the definition covers retention, cost, returned fields, safety, and the follow-up tool. Missing only pagination/ordering behavior and any note on empty results, which are minor for a per-client list.

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 coverage is 100% and the single clientId parameter is documented in the schema (from list_clients), so baseline is 3. The description adds no further meaning about clientId, nor filtering/ordering options, which is acceptable given only one required parameter exists.

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+resource: listing a client's stored keyword lookups and saved keyword lists, and enumerates what is returned for each (fields for lookups, fields for lists). It also names the sibling that opens a single item (get_keyword_research), so an agent can distinguish it from get_keyword_research and manage_keyword_list without opening schemas.

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?

Clearly scopes usage to browsing/discovery and explicitly routes to get_keyword_research for reading one lookup. It does not address when to prefer manage_keyword_list or research_keywords, so alternatives are only partially covered.

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