Skip to main content
Glama

SEO Rank Fixer

Write a fix with AI

write_fix

Writes the fix for one opportunity with SEO Rank Fixer's AI Fixer: new title and meta description options, a content refresh brief, an answer block, or a plan for competing pages. Nothing on the site is changed.

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": {
      "fixId": "<fixId>"
    },
    "name": "write_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixIdYesA fix id from top_fixes or opportunities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, which on its face looks contradictory for a verb like "write". The description resolves that ambiguity explicitly with "Nothing on the site is changed", telling the agent this is server-side AI generation rather than a live site mutation. It does not mention that idempotentHint=false means repeated calls yield fresh AI output, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and outcome types, closing on the reassuring non-mutation caveat. Nothing is padded or repeated from the title.

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 one required parameter and no output schema, the definition is nearly sufficient, and the enumerated artifact types act as a lightweight return description. It still leaves the agent unsure whether calls are billable or repeatable, and no mention of the non-idempotent generation behavior.

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?

Schema description coverage is 100% and the fixId description already names top_fixes and opportunities as sources, so the schema does the work. The description's "for one opportunity" reinforces single-id scope, but adds no format or validation detail beyond the schema.

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?

A concrete verb plus resource ("Writes the fix for one opportunity") followed by an enumeration of the artifact types it can produce: title/meta options, content refresh brief, answer block, competing-page plan. An agent knows exactly what it gets back. It stops short of naming a sibling that reads results back (fix_results) to complete the differentiation.

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?

The phrase "for one opportunity" plus the schema note that fixId comes from top_fixes or opportunities implies the correct entry points, but it never states when to choose this versus fix_results, content_briefs, or ai_answers, and gives no exclusions or prerequisites.

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.