Skip to main content
Glama

SEO Rank Fixer

Top fixes

top_fixes
Read-onlyIdempotent

The SEO fixes worth the most extra clicks right now, each with why it matters and the steps to take; a fix about one search can also have its keyword difficulty (0-100) and search intent. Optionally for one site. Every fix is available through opportunities.

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

Input Schema

NameRequiredDescriptionDefault
siteIdNoA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 safety behavior needs no restating. The description contributes useful payload detail (each fix carries 'why it matters and the steps to take', plus keyword difficulty 0-100 and search intent where applicable), but says nothing about ordering guarantees, result limits or freshness of 'right now'.

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

Conciseness3/5

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

It is short, but the opening is a verbless fragment front-loaded with vague intensifiers ('worth the most extra clicks right now'), and the semicolon chain packs the optional scope and the sibling cross-reference into the tail. Every idea is relevant, yet the ordering of information is awkward rather than crisp.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so reasonably well: prioritized fixes with rationale, remediation steps, and conditional keyword difficulty and intent fields. Gaps remain around result count, ordering stability, and whether a fix can recur across calls.

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?

With one parameter at 100% schema coverage, the schema already documents siteId as a UUID from list_sites. The description only echoes optionality ('Optionally for one site') and adds no scoping nuance, such as what the default across all sites means. Baseline 3 is appropriate.

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 resource and its ranking criterion explicitly: SEO fixes ordered by 'worth the most extra clicks right now', with rationale and steps attached. It also implies the relationship to the sibling 'opportunities' ('Every fix is available through opportunities'), which is a real differentiation, though the boundary is stated as a footnote rather than a clear contrast.

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 is only implied: 'right now' and 'worth the most extra clicks' suggest the prioritization use case, and the opportunities sentence hints that this is a filtered subset. There is no explicit when-to-use/when-not-to guidance, and no prerequisites such as whether a scan must have run first.

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.