Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Keyword metrics

keyword_overview
Read-only

Google search volume, CPC, competition, keyword difficulty (0–100) and main search intent for up to 100 keywords in one call. About $0.01 per call plus $0.0001 per keyword.

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": {
      "keywords": "<keywords>"
    },
    "name": "keyword_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to look up (max 100).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new context the annotations cannot convey: the concrete pricing model ($0.01 per call plus $0.0001 per keyword), which materially affects how an agent should batch requests. It doesn't mention latency, rate limits, or failure behavior for invalid locations.

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, zero filler: the first front-loads what is returned, the second front-loads cost. Every clause carries actionable 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 read-only metric lookup, the description enumerates the return fields (compensating for the absent output schema) and discloses cost. Combined with a fully documented schema, an agent has everything needed to invoke it correctly.

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 description coverage is 100% — the keywords, language_code, and location_code parameters are already fully documented with examples and defaults. The description repeats the 100-keyword cap but adds no new meaning about parameter behavior, so the baseline of 3 applies.

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 names the exact metrics returned (search volume, CPC, competition, keyword difficulty 0–100, main search intent) and the batch limit, so an agent knows precisely what this tool produces. It stops short of distinguishing itself from siblings like keyword_ideas or keyword_suggestions, which also relate to keywords.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for up to 100 keywords in one call' implies this is the bulk metrics lookup, and the cost line hints at budget considerations. However, it never states when to prefer this over keyword_ideas, keyword_suggestions, or keyword_gap, leaving the routing decision to inference.

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