@true402.dev/mcp-server

ranked_keywords

Which keywords a domain already ranks for in organic search, with position, search volume, CPC and competition. POST { target }; unpaid returns 402.

Instructions

Which keywords a domain already ranks for in organic search, with position, search volume, CPC and competition. POST { target }; unpaid returns 402. (PAID x402 service — USDC on Base; the MCP server needs a funded wallet to settle.) Price: $0.05 USD (fixed).

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

Name	Required	Description
`limit`	No	Rows to return, 1-200, default 50
`target`	Yes	Domain, or any URL on it
`language`	No
`location`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Oct 22, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well on the biggest behavioral trait: it discloses that this is a paid x402 service, that an unpaid call returns 402, that settlement is USDC on Base, and that a funded wallet is required, plus a fixed $0.05 price. It omits that the POST is a read-only query (no mutation warning needed) and says nothing about rate limits or other error modes.

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?

Three short sentences with the data description front-loaded, followed by the call shape and the payment caveat. No filler, though the parenthetical payment detail is dense and slightly buried mid-sentence.

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

Completeness3/5

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

There is no output schema, and the description helpfully names the returned fields and the payment flow, which covers the major unknowns. However, it leaves the language/location parameters and any pagination or result-limit behavior unexplained, which matters for a 4-parameter query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 'target' is hinted at ('a domain') and nothing is said about limit, language or location. With schema description coverage at 50%, the description needed to compensate for the two undocumented parameters and does not — an agent gets no guidance on how language/location shape results.

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 states a specific resource and scope: keywords a domain already ranks for in organic search, and it enumerates the returned metrics (position, volume, CPC, competition). That implicitly separates it from keyword_ideas and keyword_volume, though neither sibling is named explicitly.

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 implied by 'already ranks for' — use this for existing organic rankings rather than new keyword discovery — but the description never states when to prefer it over keyword_volume, keyword_ideas or serp. No exclusions or prerequisites beyond the payment note.

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