Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Site setup status

sites_setup_status
Read-onlyIdempotent

What is set up for a site and what is left, in order: the tracking code, Google Search Console, past analytics, the business profile, goals, optional measurement and team. Each step says whether it is done, what Sextant sees, who can do it ("you": the person in the Sextant app; "you or your AI": an agent too) and the actions to use. It is the starting point for setting up a site.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile needs no restating. The description instead adds real substance beyond them: the ordered list of steps and, importantly, what each step reports (done/not done, what Sextant observes, who can perform it, and which actions to use), including the meaning of the "you" vs "you or your AI" labels. It does not cover failure behavior when a site is unconfigured or the meaning of "what Sextant sees" in detail, which keeps it from a 5.

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 answer is front-loaded ("What is set up ... and what is left") followed by an ordered enumeration and a closing usage pointer. The parenthetical explaining the "you"/"you or your AI" labels is necessary disambiguation rather than padding. Slightly dense single-paragraph phrasing, 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 output schema, the description carries the burden of describing the return shape, and it does so well by naming each step and the four things reported per step. Annotations cover the read-only safety profile, so little else is required. The remaining gap is the undocumented siteId, which an agent must resolve from elsewhere.

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?

The single parameter siteId has 0% schema description coverage and the description never mentions it, say nothing about accepted format (numeric id, domain, slug) or where to obtain it. With low coverage the description is expected to compensate, and here it adds nothing on the parameter side. The parameter is intuitively named, which prevents a 1.

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 makes clear this is a setup-readiness/checklist report for a single site, enumerating the exact steps it covers (tracking code, Search Console, past analytics, business profile, goals, measurement, team). The verb is implicit ("what is set up ... and what is left") rather than an explicit action, and no sibling such as google_setup_status or integrations_status is named to distinguish it. Still, an agent can tell what the tool is for without opening the schema.

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?

"It is the starting point for setting up a site" gives clear situational context for selecting this tool before the individual setup steps. There are no exclusions or explicit alternatives, so an agent is left to infer when a narrower sibling (e.g. google_setup_status) would be preferable. Clear context without when-not guidance fits a 4.

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