Skip to main content
Glama

SEO Rank Fixer

All opportunities

opportunities
Read-onlyIdempotent

Every open SEO opportunity, highest estimated gain first, filterable by site and type, with keyword difficulty and search intent where known.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly one kind of opportunity.
limitNo
offsetNo
siteIdNoA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value by disclosing the default sort ('highest estimated gain first') and that difficulty and intent are only sometimes present, but says nothing about pagination or result caps.

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?

One compact sentence that front-loads the scope, ordering, and filterability with no wasted words. Every clause carries information the agent needs.

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?

For a read-only list tool with no output schema, the description covers ordering and returned attributes but omits pagination defaults and maximum page size, which matter given the 100-row limit. It is adequate but not fully sufficient to call blindly.

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?

At 50% schema coverage, type and siteId are already documented in the schema, and the description only restates that filtering is possible. The limit and offset parameters are undocumented in both schema and description, so default page size and paging behavior remain unclear.

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 gives a specific resource (open SEO opportunities) plus scope (all, open, ranked by estimated gain) and available attributes. It does not name a sibling such as top_fixes or competitor_gap, so an agent must infer the difference, which keeps it below a 5.

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 implied by 'Every open SEO opportunity' and the site/type filters, suggesting this is the broad listing tool. There is no explicit when-to-use or when-not-to-use guidance and no pointer to the narrower siblings that likely cover subsets.

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.