Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

What history can be imported

imports_sources
Read-onlyIdempotent

How to bring a site's older analytics into Sextant: which days can be imported (up to the day before Sextant's first tracked day), the size limit, whether Google Analytics is connected, the CSV template for every other tool (HubSpot, Plausible, Fathom, Matomo, Simple Analytics, Universal Analytics, spreadsheets), and the import running now. Start here. Admin.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the payload contents (cutoff day, size limit, connector state, CSV template per tool, current import) and appends 'Admin.', signalling an admin permission requirement. It does not say what happens when GA is not connected, but the disclosure level is well above the annotation baseline.

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

Conciseness3/5

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

The core statement is front-loaded, but the middle collapses into a long comma-separated inventory of tools and return fields that is dense to parse. Trailing single-word fragments ('Start here. Admin.') are efficient but ambiguous as to what they attach to.

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 must describe the return payload, and it does so item by item — cutoff dates, size limit, GA connection, CSV templates, running import. For a read-only, single-parameter capability probe this is close to sufficient; only the siteId meaning and the no-GA branch are left 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?

There is a single required parameter, siteId, with 0% schema description coverage, so the description carries the burden — and it says nothing about siteId or its format. That said, the parameter is self-evident in context, so the gap is small rather than severe.

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 names a concrete resource — a site's importable history in Sextant — and enumerates exactly what it reports (importable days, size limit, Google Analytics connection state, CSV template, currently running import). That is much more specific than the title alone. It stops short of a clean verb phrase like 'returns import capabilities for a site', reading more like a help-article summary, but an agent can still tell what the tool does and that it differs from imports_list/imports_status.

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?

'Start here' is an explicit entry-point directive, and the mention of GA connection state hints at a prerequisite check before imports_ga4_properties. However, it never states when NOT to use this tool, and 'the import running now' overlaps with the sibling imports_status without explaining which to prefer for live import progress. Usage is implied rather than spelled out.

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