Skip to main content
Glama
Sign In

Measure.events Analytics

by io.github.meetclawdius
OverviewDiscussionsAdmin

Site analytics

get_site_analytics
Read-only

Pageviews, visitors (humans), AI agent and bot requests, top pages and referrers for a period.

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": {
      "site_key": "<site_key>"
    },
    "name": "get_site_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, YYYY-MM-DD (UTC, inclusive).
fromNoStart date, YYYY-MM-DD (UTC, inclusive).
periodNoTime period. Ignored when from and to are given.
site_keyYesThe site's tracking ID (site_key), from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"Start date YYYY-MM-DD (for custom range)"New value: +"Start date, YYYY-MM-DD (UTC, inclusive)."
    • changedInput schema / properties / period / description
      Previous value: -"Time period (default: month)"New value: +"Time period. Ignored when from and to are given."
    • changedInput schema / properties / period / enum
      Previous value: -[
-  "day",
-  "week",
-  "month",
-  "year"
-]New value: +[
+  "24h",
+  "7d",
+  "30d",
+  "90d",
+  "year",
+  "day",
+  "week",
+  "month"
+]
    • changedInput schema / properties / site_key / description
      Previous value: -"The site's tracking ID (site_key)"New value: +"The site's tracking ID (site_key), from list_sites."
    • changedInput schema / properties / to / description
      Previous value: -"End date YYYY-MM-DD (for custom range)"New value: +"End date, YYYY-MM-DD (UTC, inclusive)."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already carry the safety profile, so the description need not restate it. It adds useful content context by distinguishing human visitors from AI agent and bot requests, but says nothing about aggregation granularity, top-N limits, or data freshness.

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?

A single compact sentence with no filler, front-loading the primary metrics before the dimension breakdown and referrers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only analytics tool with no output schema, the description conveys the broad contents but leaves open how results are grouped, whether top pages/referrers are truncated, and how it differs from sibling reporting tools. Adequate but with clear gaps.

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 coverage is 100% and the schema explains the from/to inclusive UTC dates and that period is ignored when from and to are given. The description's 'for a period' adds nothing beyond that, so the baseline of 3 is appropriate.

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 enumerates the exact data the tool returns: pageviews, human visitors, AI agent and bot requests, top pages and referrers. That is specific enough for an agent to know what it gets, but it omits a verb and never distinguishes it from near-siblings like get_site_summary, get_breakdown, or get_agent_report.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus get_breakdown, get_site_summary, or get_agent_report, and no mention of prerequisites or defaults (e.g., what happens if no period/from/to is supplied). The agent must infer usage from the metric list alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Measure.events Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources