Skip to main content
Glama

SEO Rank Fixer

Fix results

fix_results
Read-onlyIdempotent

Whether the fixes worked: every fix marked done on one site, when it went live, and its Google clicks and position in the 4 weeks before and after (bad results included), plus problems that are gone. Use it to answer "is SEO Rank Fixer working?" with the site's own numbers.

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": "fix_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: results include bad outcomes rather than only wins, and the measurement window is a fixed 4 weeks before and after go-live. It says nothing about empty states (a site with no marked-done fixes), result ordering, or size, so it stops short of rich behavioral disclosure.

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 sentences, front-loaded with the returned content and then the use case; each clause (go-live date, before/after window, bad results included, resolved problems) carries distinct information. It is dense but not padded, with only mild cost from the parenthetical aside.

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 one required parameter, read-only annotations and no output schema, the description carries the burden of explaining the return payload and does so adequately by enumerating the fields and the measurement window. Minor gaps remain around the shape of 'problems that are gone' and behavior when no fixes are marked done.

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 with 100% schema description coverage that already points the caller to list_sites for the UUID. The description adds no further meaning about siteId, which is acceptable given the schema does the work, so the baseline of 3 applies.

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 the specific resource and scope: per-site results for fixes marked done, with go-live dates, Google clicks and position for the 4 weeks before and after, plus resolved problems. That is far more specific than the title 'Fix results' alone. It does not explicitly contrast itself with site_performance or rank_tracking, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives a clear trigger phrase - use it to answer 'is SEO Rank Fixer working?' with the site's own numbers - which tells an agent exactly which question this tool serves. There is no explicit when-not guidance or named alternative for adjacent questions such as raw ranking trends, which would be needed for a 5.

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.