Skip to main content
Glama

Read site analytics

siteAnalytics
Idempotent

Read one owned project’s own site traffic (not its Analytics page’s devices or a row’s detail), with the counter’s state (site): a count is only meaningful next to whether anything is counting it. The first read of a project that never had a key issues its public siteKey, exactly as opening the Analytics page does — so this read can create that key as a side effect. notes and site.notice are the answer’s own sentences, and traffic.available distinguishes unavailable traffic storage from measured traffic: false means this deployment has no traffic store, so nothing is counted and no key can be issued — notes says so in the page’s words rather than returning a zero that reads as “no visits”. With visitorsCounted: false every unique-visitor count is null: unmeasurable, not zero. Aggregates only: no visitor is identified, no row is returned, and this cannot change what a visitor’s page counts. Another account’s project answers not found.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
timeZoneNo
projectIdYes

Output Schema

NameRequiredDescriptionDefault
siteYes
notesYes
windowYes
hostingNo
trafficYes
projectIdYes
retentionDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, and the description earns that by disclosing the key-issuing side effect on first read of a project without a key. It further explains traffic.available=false meaning no traffic store and no key issuance, visitorsCounted=false meaning null rather than zero counts, and that other accounts' projects return not-found — rich behavioral context beyond the annotations.

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?

Purpose is front-loaded and almost every sentence carries real information, but the prose is one long em-dash-laden block with nested asides that impede scanning. A short structured breakdown of side effects and null semantics would convey the same content more efficiently.

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?

An output schema exists, so the description's explanations of notes, site.notice, traffic.available, and visitorsCounted are bonus context rather than obligations. The remaining hole is parameter guidance for the day window and timezone, which an agent needs to call this correctly.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, and the description never mentions days, timeZone, or projectId semantics — no defaults, no accepted formats, no timezone interaction with the day window. With no schema documentation to fall back on, this is a significant gap the description should have filled.

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 opening clause names a specific verb and resource ('Read one owned project's own site traffic') and immediately scopes it against adjacent concepts ('not its Analytics page's devices or a row's detail'). The core purpose is discernible, but the dense parenthetical phrasing makes the agent work harder than necessary to extract it.

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 carves out what this is not (device breakdowns, row detail) and implies usage for aggregate traffic counts, but it never names an alternative tool or states a when-not condition tied to a concrete task. Guidance is implied rather than actionable.

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