Skip to main content
Glama

SEO Rank Fixer

Get listed plan

listing_plan
Read-onlyIdempotent

A checklist of legitimate places to list one site to earn its first backlinks and visibility (Google Business Profile, Bing, social profiles, review sites, software directories, local directories), picked for the kind of site, with why each one matters, the steps, cost, effort, link type, and the user's status (todo, submitted, live, skipped) and last link check. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

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?

With no output schema, the description usefully discloses the payload shape: per-item rationale, steps, cost, effort, link type, status values (todo, submitted, live, skipped), and last link check. The trailing 'Read-only' merely restates readOnlyHint/non-destructive annotations and adds nothing, and no note is given about whether the plan is generated on the fly or persisted.

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?

The core purpose is front-loaded in the opening clause and the parenthetical list plus field enumeration is informative rather than padded. It is one very long sentence, and the closing 'Read-only' is redundant with annotations and could be dropped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only tool with no output schema, the description covers the resource, its tailoring logic, and the exact fields/status values returned. Combined with full schema coverage of siteId and annotations covering safety, an agent has what it needs to call it and interpret results.

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?

Schema description coverage is 100% and the single siteId is already documented as 'A site id from list_sites' with a UUID pattern. The description adds no further meaning about the parameter, so the baseline 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 concrete resource — a checklist of listing destinations (Google Business Profile, Bing, social profiles, review sites, directories) tailored to a site — so an agent knows exactly what comes back. It lacks an explicit verb and never distinguishes itself from nearby siblings such as product_listings or opportunities, 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 Guidelines3/5

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

Usage is only implied: 'to earn its first backlinks and visibility' signals an early-stage/off-page SEO scenario, and 'picked for the kind of site' hints at tailoring. There is no explicit when-to-use versus alternatives, no mention of list_sites prerequisite in the description text, and no exclusion of overlapping tools like product_listings.

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.