Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a site

sites_get
Read-onlyIdempotent

A site's name, domain, effective workspace plan (free, hobby or pro; legacy contracts retain their version), default time zone, country and language, your level on it, and what it is built with (builder, builderName) and where it is edited (builderUrl). builder and builderUrl say where a change to the website itself has to go.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety is covered. The description adds real value by disclosing the exact read surface and by explaining that builder/builderName/builderUrl tell you where site edits must be made, but it says nothing about behavior for an invalid or unknown siteId (error vs empty result).

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?

Two sentences with no filler; every listed field carries information an agent would otherwise have to discover empirically. It is slightly dense as a single long enumeration rather than front-loading 'Returns a single site's…', but nothing 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 output schema, the description usefully stands in for one by enumerating the returned fields and clarifying the builder/builderUrl semantics. For a single-parameter read tool with annotations covering safety, the only meaningful gap is the siteId input contract.

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?

Schema description coverage is 0% and the single parameter siteId is never mentioned in the description. It does not clarify whether siteId accepts only an internal ID or also a domain, nor whether it must come from list_sites, so the description fails to compensate for the coverage gap despite the obvious parameter name.

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 effectively names the resource and enumerates exactly what is retrieved about a single site (name, domain, plan, timezone, country, language, user level, builder info). It doesn't explicitly frame itself as 'fetch one site by ID' nor contrast with list_sites, but an agent can infer single-site retrieval versus listing.

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 when-to-use guidance, no mention of prerequisites such as needing a siteId that the caller already knows, and no routing to siblings like list_sites (to discover IDs) or sites_ceilings_get / billing_site (for plan or billing detail). Usage is only implied by the field list.

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