Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Keywords a domain ranks for

ranked_keywords
Read-only

Google organic keywords a domain (or URL) currently ranks for, sorted by estimated traffic: keyword, volume, difficulty, position, ranking URL and estimated traffic. About $0.01 per call plus $0.0001 per row.

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": {
      "target": "<target>"
    },
    "name": "ranked_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1–200 (default 50).
targetYesDomain such as example.com.
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context – live Google organic data, traffic-sorted output, and a concrete cost model ($0.01/call + $0.0001/row) – but says nothing about data freshness, database scope, or result truncation beyond the limit parameter.

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 tight sentences: the first front-loads what the tool returns and its sort order, the second gives the cost. No filler, no restating of the tool name.

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?

With no output schema, the description correctly takes on the job of enumerating return fields (keyword, volume, difficulty, position, ranking URL, traffic) plus pricing and sort order. What remains unstated – data freshness and whether results are a full or sampled set – is minor for a read-only keyword lookup.

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, and the description earns an increment by clarifying that 'target' accepts a URL as well as a bare domain – information the schema's 'Domain such as example.com' wording does not convey – and by establishing that results are sorted by estimated traffic.

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 gives a specific verb and resource ('Google organic keywords a domain (or URL) currently ranks for') and enumerates the returned fields, so the agent knows exactly what comes back. It does not name any sibling (keyword_overview, keyword_gap, domain_overview) to distinguish when this one is the right pick.

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?

Usage is only implied: 'currently ranks for' suggests a live ranking snapshot for a known domain. There is no explicit when-to-use/when-not guidance and no reference to the competing keyword_* or domain_overview siblings.

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