Skip to main content
Glama

SEO Rank Fixer

List sites

list_sites
Read-onlyIdempotent

Lists the websites in the user's SEO Rank Fixer workspace, with their ids, sync status and the date their Search Console data runs through, and the account's plan and site allowance.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond them by disclosing the return contents, notably that the account's plan and site allowance come back here, which lets an agent check quota without a separate call; it does not mention scope/permission requirements beyond 'the user's workspace'.

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?

A single front-loaded sentence with the core purpose first and return details trailing. It is slightly comma-chained ('and the date their Search Console data runs through, and the account's plan...'), which costs a little readability, but no sentence is wasted.

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 no parameters and no output schema, the description carries the burden of describing the response, and it does so reasonably by naming the key returned fields. It could be slightly more explicit about the response shape (a collection of sites plus an account object), but nothing critical for correct invocation is missing.

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?

The tool takes no parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies the list is implicitly scoped to the caller's workspace rather than requiring a workspace or user argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists the websites in the user's SEO Rank Fixer workspace') and then enumerates what comes back: ids, sync status, Search Console data-through date, plan and site allowance. That makes it clearly the workspace-wide enumeration entry point, distinguishable from per-site siblings such as site_profile or site_audit without opening any schema.

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: as a zero-parameter lister, it reads as the discovery call to make before per-site tools, but the description never says 'call this first' or names an alternative. With only one obvious behavior there is little risk of misuse, but no explicit when-to-use guidance is given.

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.