Skip to main content
Glama

Analytics snapshot

analytics_snapshot
Read-onlyIdempotent

Analytics snapshot for one website: requested window, series, prior period, and the channel recommendation. from/to default to the last 60 days in time_zone (UTC if omitted).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analytics_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoinclusive end YYYY-MM-DD; default today
fromNoinclusive start YYYY-MM-DD; default last 60 days
periodNonamed window instead of from/to: today, yesterday, 7d, 28d, 30d, 90d, 365d (each ends today), this_month, or last_month
currencyNolowercase ISO 4217 code
time_zoneNoIANA time zone; default UTC
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website
granularityNoday, week, or month; default day

Output Schema

NameRequiredDescriptionDefault
tierYes
priorYes
scopeYes
cohortYes
seriesYes
app_urlNo
qualityYes
activityYes
channelsYes
headlineYes
website_idYes
recommendationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context: the window defaults resolve to the last 60 days computed in time_zone (UTC if omitted), and it discloses the shape of the response (window, series, prior period, recommendation).

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and its contents, followed by the default-resolution rule. No filler, no restatement of the title, and nothing that could be cut without losing information.

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 a seven-parameter, all-optional read tool with an output schema and full annotation coverage, the description supplies the essentials without redundantly explaining return values. It stops short of describing cost, caching, or how prior-period comparison is chosen, which would round it out for a heavy analytics call.

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 every one of the seven parameters is already documented, including the named windows, granularity values, and website_id fallback. The description adds only one nuance — that from/to defaults are computed in time_zone rather than UTC — which is largely inferable from the two schema entries.

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 the resource (an analytics snapshot for one website) and enumerates what the snapshot contains: requested window, series, prior period, and channel recommendation. It is specific enough to distinguish from siblings like insights or journey_detail, though it never explicitly contrasts with them.

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?

Usage is implied ('snapshot for one website') but there is no explicit when-to-use statement, no exclusions, and no pointer to an alternative when the agent wants a different analytical view. The default-window note is helpful context but not routing guidance.

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