Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Keyword ideas, keyword research

keywords_ideas
Read-only

Keyword ideas for SEO and ads: the search phrases real users type for a seed keyword, from Google, Bing, YouTube, Amazon and DuckDuckGo autocomplete, deduplicated and ranked by how many engines suggest each, with question and buying-intent phrases listed apart. deep=true adds the Google long tail (seed + a-z, how, what, best, vs), up to 200 keywords. Use to plan content, find long-tail and question keywords, or name a product. No search volumes. Example: seed=crm software. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "keywords_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
deepNotrue to add the Google long tail (seed + each letter, question words); about 30 more lookups
langNoLanguage code (default en)
seedYesSeed keyword or topic, 2-80 characters
countryNoCountry code (default us); Amazon suggestions come from that country's store where one exists
enginesNoOptional comma list: google, bing, youtube, amazon, duckduckgo (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only/open-world/non-idempotent; the description adds substantial context beyond them: cost of $0.01 per call, 25 free calls, failed calls free, and an explicit explanation that repeats are not free (which reconciles the idempotentHint=false). It also discloses the ranking/dedup behavior and the ~200 keyword ceiling, none of which annotations convey.

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?

The core capability, the deep flag, the use cases, and the pricing are front-loaded in that order with no filler. The opening sentence is long and carries several clauses, but every clause adds distinguishing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, no-output-schema paid tool, the definition covers output shape (deduplicated, ranked, question vs buying-intent split), size limit, cost model, and side effects. An agent has everything needed to decide, budget, and invoke correctly.

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, but the description adds a total output ceiling (up to 200 keywords) and a worked example (seed=crm software) that the schema lacks. It leaves the interplay of lang/country/engines to the schema, which is adequate given full coverage.

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 specific resource and mechanism: search phrases real users type for a seed keyword, aggregated from five named autocomplete engines and deduplicated/ranked. It also carves out what the tool is not ('No search volumes'), which distinguishes it from a metrics tool and from the sibling text_keyword_density.

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 concrete when-to-use cases: plan content, find long-tail and question keywords, or name a product, and explains what the deep flag buys in that context. It stops short of naming an explicit alternative tool or stating when-not to use it, so it lands at 4 rather than 5.

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.