Skip to main content
Glama
SpeedyIndex MCP server

SpeedyIndex MCP server

Keyword positions

rank_positions
Read-only

Get Google keyword positions for a project from the latest or selected check, showing movement from the previous check and filtering to only changed keywords.

Instructions

Google positions of a project's keywords in a check (latest finished by default), with the change against the previous check. changed_only returns only keywords that moved.

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": {
      "project_id": "<project_id>"
    },
    "name": "rank_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
tagNo
check_idNo
region_idNo
project_idYes
changed_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish this as a read-only, open-world query, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: which check is selected by default (latest finished) and that a delta against the previous check is computed. It says nothing about result volume, ordering, or what limits apply.

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 tight sentences with the core behavior and the default check selection front-loaded. Nothing is wasted, though the changed_only clause could have been folded more tightly into the main 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?

With no output schema, the description does sketch the return content (positions plus change vs previous check), which is the minimum needed. However, for a 6-parameter tool with zero schema documentation and a 5000-row cap, an agent still lacks enough to filter or paginate confidently.

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?

Schema description coverage is 0%, so the description carries the full burden and largely fails it. It clarifies check_id (latest finished by default) and changed_only, but leaves max, tag, region_id, and project_id entirely unexplained, including the 500 default / 5000 cap on max.

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 a specific verb+resource: it returns Google positions of a project's keywords and the change against the previous check. That is concrete enough to separate it from rank_keyword_details or rank_projects, though it never explicitly names those siblings.

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?

'a check (latest finished by default)' implies the default behavior and when to pass check_id, and 'changed_only returns only keywords that moved' hints at a reporting use case. But there is no explicit when-to-use versus alternatives such as rank_keyword_details, and no guidance on combining tag/region filters.

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