Skip to main content
Glama

SEO Rank Fixer

Rank tracking

rank_tracking
Read-onlyIdempotent

The latest daily Google position (organic, top 30 checked) of each search the user tracks for a site, with the change over 1, 7 and 30 days, the best position so far, the ranking page and the SERP features Google shows (AI overview, featured snippet, people also ask, local pack). Read-only: it reads stored checks and never starts a new one.

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": {
      "siteId": "<siteId>"
    },
    "name": "rank_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

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, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: it discloses that positions are organic, capped at top 30, based on the latest daily stored check (a staleness characteristic), and that no new check is started. It does not mention pagination or volume limits, which keeps it off a 5.

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?

Front-loaded: the core payload (latest daily Google position per tracked search) leads, with the field enumeration after it and the read-only constraint last. The parenthetical SERP-feature list is long but each item is informative. Slightly dense as a single running sentence, but no sentence is wasted.

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 burden of describing return values and does so thoroughly, including the fixed 1/7/30-day comparison windows that explain why no date-range parameter exists. Only minor gaps remain (result volume, whether empty/no-data cases are distinguished), so it is close to complete for a single-parameter read tool.

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?

There is a single parameter and schema description coverage is 100%, with the schema already telling the agent the value is a UUID sourced from list_sites. The phrase 'for a site' reinforces scoping but adds no format or constraint detail beyond the schema, so this sits at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns the latest daily Google organic position for each tracked search on a site, and enumerates the returned fields (change over 1/7/30 days, best position, ranking page, SERP features). The closing read-only clause differentiates it from any scan/refresh sibling by making clear it never triggers a new check.

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 context is implied rather than stated: 'reads stored checks and never starts a new one' tells an agent this is the retrieval path for existing rank data, not a fetch-fresh path. However, no alternative is named and no explicit when-to-use/when-not conditions are given, so the agent must infer whether this or a report/performance sibling is the right call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.