Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Rankings Tool

adataforseo.rankings

Read keyword ranking positions for this site across past runs and compare changes from the previous run to identify ranking trends.

Instructions

Read-only. Tracked positions of this site per keyword over the last runs, with the change since the previous run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adataforseo.rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

B3.3/5.0
Behavior3/5

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

Annotations are empty, so the description carries the full burden. It does disclose the read-only nature and the temporal scope ('last runs', delta since previous run), which is real behavioral value, but it omits how many runs are covered, whether data can be empty for a new site, or any authorization/rate-limit context.

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?

Two short sentences with no wasted words, and the read-only constraint is stated up front. Leading with the safety flag ahead of the actual purpose slightly weakens front-loading of what the tool returns.

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?

For a zero-parameter read tool with no output schema, the description is adequate but thin: it does not say how many runs 'last runs' covers, what the result rows contain, or how an agent should interpret the change value.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description usefully clarifies that the site scope is implicit rather than a parameter.

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 verb+resource: tracked keyword positions for the current site, with deltas versus the previous run. It is distinguishable from auditing-style siblings like audit, coverage, and matrix, though it never names an alternative to sharpen that distinction.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of when another tool would be preferred. 'Read-only' hints at safety but not at selection between this and siblings such as matrix, serp, or coverage.

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