Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get a website annotation

analytics_getWebsiteAnnotation
Read-onlyIdempotent

Returns the date, all-day setting, and note for a specific website annotation.

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>",
      "annotationId": "<annotationId>"
    },
    "name": "analytics_getWebsiteAnnotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
annotationIdYesID of the annotation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety profile is covered. The description adds the return shape (date, all-day setting, note), which is genuinely useful since no output schema exists, but says nothing about behavior when the ID is unknown or how siteId/objectId scoping affects the 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?

A single front-loaded sentence with no filler; the verb and the returned fields come first. It is efficient, though its brevity is close to under-specification rather than model conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-required-parameter read tool with full annotation coverage, no output schema, and no nested objects, the definition supplies the essential missing piece — what comes back. What remains (not-found behavior, full field list) is minor at this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (including the optional objectId override) are already documented in the schema. The description adds no parameter-level meaning — the fields it lists are return values, not inputs — so the baseline 3 applies.

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?

States a specific verb and resource ("Returns ... for a specific website annotation") and even names the payload fields (date, all-day setting, note). It reads as a single-record fetch, distinguishable in intent from the plural listing sibling, though it never names that sibling explicitly.

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?

No when-to-use or when-not-to-use guidance is given. The phrase "a specific website annotation" weakly implies you must already hold an annotationId (rather than enumerating annotations), but the description never points to analytics_getWebsiteAnnotations for discovery or states any prerequisite.

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