Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List sites

list_sites
Read-onlyIdempotent

Every Sextant site you can open, with your level on each one. Use a site's id as siteId in other tools.

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety is fully covered. The description adds two genuinely useful behavioral facts beyond that: results are permission-scoped ("you can open") and each item carries the caller's access level. It says nothing about ordering or pagination, so it is modest added value rather than rich disclosure.

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 result set and its access scope, then the follow-up instruction. Nothing is redundant or padded.

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 needs to convey the return shape, and it does so at the right granularity (all accessible sites, each with the user's level). Minor gaps remain around ordering and whether inactive sites are included, but nothing blocks a correct first call.

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 zero parameters, so the baseline of 4 applies; there is no parameter semantics to add beyond what the empty schema shows. The mention of the id-to-siteId mapping is about output usage rather than input meaning, which is handled under usage guidelines.

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?

Specific verb+resource ("Every Sextant site you can open") with an access-scope qualifier that separates it from sites_get or sites_ceilings_get by implying enumeration rather than single-resource lookup. It also states what comes back ("your level on each one"), so an agent knows this is a discovery call, not just a raw list. No sibling is named explicitly, which keeps it from 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 Guidelines4/5

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

The second sentence gives concrete downstream guidance: take a site's id and pass it as siteId to other tools, which establishes this as the entry point in a chain. It does not state when to prefer sites_get or seo_list_search_console_sites, so alternatives remain inferred rather than spelled out.

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.

Resources