Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List website annotations

analytics_getWebsiteAnnotations
Read-onlyIdempotent

Returns a paginated list of dated notes for the website, optionally filtered by date range or search text. Dates: leave them out for every note, or pass range or startDate and endDate to narrow.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
endAtNoEnd of the date range as a Unix timestamp in milliseconds.
rangeNoA preset from the app's date picker, in the site's time zone. 7d, 30d, 90d: today and the days before it, from local midnight. 24h: the current hour and the 23 before it. 12m, 24m, 36m: this month and the months before it, from the 1st. month: this month. today: since local midnight. It gives the same numbers as the app. Leave out the other date fields when you use it.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
endDateNoLast day of the range (YYYY-MM-DD), included to its end in the site's time zone. An ISO date-time is used as is.
startAtNoStart of the date range as a Unix timestamp in milliseconds.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
pageSizeNoNumber of results per page.
startDateNoFirst day of the range (YYYY-MM-DD), from local midnight in the site's time zone. An ISO date-time is used as is.
maxResultsNoMaximum number of results to include.

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, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavior on top: results are paginated, and omitting all date fields returns the full unfiltered set rather than a default window. It does not mention ordering, default page size, or result caps.

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, front-loaded with the core purpose and followed by the date rule. The date sentence partially duplicates the schema's own wording, which is the only real waste.

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?

For an 11-parameter read tool with no output schema, the description plus the fully documented schema covers what an agent needs: resource, pagination, and the default unfiltered scope. Interaction between pageSize and maxResults, and the meaning of a returned note, are left to the schema or unstated.

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 the schema already explains range presets, timestamp fields, ISO dates, paging, and objectId. The description only restates the mutually exclusive date strategy, adding little beyond what the schema says, 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?

The description gives a specific verb and resource: a paginated list of dated notes for a website, with optional date-range or search filtering. That is clearly distinct from aggregate-metric siblings, though it never names the singular analytics_getWebsiteAnnotation sibling, so the agent must infer the singular/plural split.

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

Usage Guidelines3/5

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

It gives real guidance on the date axis: omit dates to get every note, or narrow with a range or startDate/endDate. It does not say when to pick this tool over the singular annotation tool or the other analytics listing tools, so tool selection is only implied.

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