Skip to main content
Glama

Look up keyword ideas

lookup_keywords

Keyword ideas from one seed: volume, difficulty, and intent. Costs 15¢ from the user's BudgetSEO balance unless the result is already cached. Tell the user the cost and wait for a yes. This is not research_keywords.

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": {
      "seed": "<seed>"
    },
    "name": "lookup_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYes
countryCodeNoTwo-letter country code. Defaults to US.

Output Schema

NameRequiredDescriptionDefault
seedYes
ideasYes
relatedYes
fromCacheYes
countryCodeYes
seedMetricsYes
creditsSpentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only mark it as non-read-only and open-world; the description goes well beyond them by disclosing a 15¢ charge against a named BudgetSEO balance, a cache path that avoids the charge, and a mandatory 'tell the user and wait for yes' gate. These are exactly the side effects and preconditions an agent cannot infer from 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?

Three short sentences, front-loaded with what the tool returns, then cost, then the confirmation rule, and a final disambiguation clause. Every sentence carries distinct decision-relevant information with no padding.

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?

An output schema exists, so the description needn't enumerate return fields, and the cost/auth/cache behavior is the key missing piece from annotations — which it covers. The remaining gap is that the difference from research_keywords is asserted rather than described, leaving the agent to infer when this cheaper single-seed call is the right choice.

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 50%: countryCode is documented in the schema while seed is not. 'From one seed' reinforces that the tool takes a single query term, but the description adds no length bounds, format expectations, or country semantics, so it does not compensate for the undocumented parameter.

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 concrete resource and scope: keyword ideas from one seed, with the three returned fields (volume, difficulty, intent). It also preempts the most likely confusion by stating 'This is not research_keywords', so an agent can distinguish it from the nearest sibling without opening either schema.

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 gives real usage conditions: a per-call cost, a cache exception that makes the call free, and a required user-confirmation step before invoking. What's missing is positive routing guidance — it says what it is not (research_keywords) but never states which task should send the agent to this tool instead.

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