Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Links to Sextant pages

sites_links
Read-onlyIdempotent

The full address of every Sextant page you can open for this site (each with what it shows), its setup steps, and its workspace's pages, so a link can lead to the exact page.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful content about what the response contains (full addresses, what each page shows, setup steps, workspace pages), which is genuine context beyond the annotations, but it says nothing about ordering, truncation, or whether sites without pages return empty.

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

Conciseness2/5

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

The single sentence is dense and oddly structured, with a nested parenthetical and a list of three loosely parallel items whose referents are unclear. It is short but not front-loaded, and the reader has to reparse it to extract the resource being returned.

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?

With no output schema, the description carries the burden of describing return values, and it does gesture at the payload (addresses, page descriptions, setup steps, workspace pages). However, the phrasing is too ambiguous to let an agent predict the response reliably, and the lone parameter is entirely unaddressed, leaving real gaps for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, siteId, at 0% schema description coverage, and the description never explains what a site ID is or where to obtain it. With schema coverage this low the description needed to compensate for the parameter gap and instead says nothing about it.

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

Purpose3/5

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

The description roughly conveys that the tool returns the addresses of Sextant pages for a site, but the sentence is garbled enough that the resource is ambiguous. 'Sextant pages', 'its setup steps', and 'its workspace's pages' are strung together without a clear statement of what the tool actually returns as a whole, so the agent has to guess at the output shape rather than recognize a verb+resource pair.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this rather than alternatives; the sibling analytics_getLinks is never acknowledged, and no prerequisites or exclusions are stated. The trailing clause 'so a link can lead to the exact page' hints at an intent but never turns it into a condition an agent can act on.

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