Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Long-tail keyword ideas

keyword_ideas
Read-only

Long-tail keywords that contain the seed keyword, with search volume, CPC, keyword difficulty and intent. Use it to find low-difficulty commercial keywords. About $0.01 per call plus $0.0001 per keyword returned.

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": {
      "keyword": "<keyword>"
    },
    "name": "keyword_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoKeywords to return, 1–200 (default 50).
keywordYesSeed keyword.
language_codeNoLanguage code, e.g. en (default), de, fr, ja, es, pt, zh-CN.
location_codeNoDataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil.
max_difficultyNoOnly return keywords with keyword difficulty at or below this value (0–100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's real contribution is cost transparency: $0.01 per call plus $0.0001 per keyword returned, which directly affects how an agent should choose the limit parameter. It omits any note on data freshness, upstream latency, or whether empty results are still billed, which would have pushed it higher.

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?

Two sentences, both front-loaded with the payoff (what you get, then why to use it) and closed with the cost caveat. Zero filler and every clause carries distinct information.

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?

All five parameters are documented in the schema, the return fields are named in the description despite there being no output schema, and pricing is disclosed. The only gap is operational detail — how cost scales with limit, result freshness, or pagination — but nothing needed to invoke it correctly is missing.

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%, including ranges, defaults, and location codes for all five parameters, so the schema already carries parameter meaning. The description reinforces that the keywords will be long-tail and contain the seed, and its 'low-difficulty' framing loosely motivates max_difficulty, but it adds no semantics the schema lacks.

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?

States a specific resource (long-tail keywords containing a seed) and enumerates the returned metrics (search volume, CPC, difficulty, intent), so an agent knows exactly what this returns. It does not name or differentiate itself from plausible siblings such as keyword_suggestions or keyword_overview, which keeps it below a 5.

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?

"Use it to find low-difficulty commercial keywords" gives a concrete selection context rather than leaving usage implied. There are no explicit exclusions or named alternatives (e.g., when to prefer keyword_suggestions over this), so the routing guidance is clear but incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CallAI SEO toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources