Skip to main content
Glama

Get Visitor Analytics

get_analytics
Read-only

The published app's visitor analytics, as the editor's Analytics tab shows them: visitors, page views and a daily trend, top pages, referrers, countries, devices, browsers and custom events (trackEvent) over a date range. Read-only. Tracking setup and consent: get_guides('analytics').

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": {
      "projectId": "<projectId>"
    },
    "name": "get_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (UTC), included. Default: today.
fromNoFirst day, YYYY-MM-DD (UTC). Default: the 30 days ending on to.
limitNoRows per list (default 25).
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the explicit "Read-only" line mostly repeats structured data. The genuinely additive part is the scoping statement that results mirror the editor's Analytics tab for the published app and that tracking/consent is a separate concern handled by get_guides. Nothing is said about empty results, data freshness, or cost of wide date ranges.

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 with the resource and scope front-loaded and the pointer to get_guides compressed into a single clause. The long metric enumeration is dense but each item is informative rather than filler.

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?

There is no output schema, so the enumeration of returned sections is essential and is provided. With 4 parameters at 75% schema coverage and full annotation coverage, the remaining gaps (projectId meaning, behavior on empty data, whether limit applies per list) are modest but real.

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 75%, so from/to/limit are already documented with formats and defaults in the schema, and the description only adds the phrase "over a date range". projectId is undocumented in both places, though "the published app's" weakly implies it identifies the project. Baseline 3 is appropriate where the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and scope — "the published app's visitor analytics, as the editor's Analytics tab shows them" — then enumerates the exact payload (visitors, page views, daily trend, top pages, referrers, countries, devices, browsers, custom events). This is far more than a restated title and lets an agent distinguish it from get_logs or get_live_payments without opening a 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?

The description establishes clear context (published-app analytics over a date range) and explicitly routes a related need elsewhere: "Tracking setup and consent: get_guides('analytics')". It stops short of stating when to prefer this over sibling read tools or what to do when there is no data, so no explicit exclusions are present.

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