Skip to main content
Glama
mikusnuz

umami-mcp

get_event_data_stats

Get summary counts of event data for a website. Specify time range and optionally filter by event name to analyze event performance.

Instructions

Get event data statistics (summary counts) for a website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteIdYesWebsite UUID
startAtYesStart timestamp in milliseconds
endAtYesEnd timestamp in milliseconds
eventNameNoFilter by event name

Implementation Reference

  • Tool 'get_event_data_stats' is registered via server.tool() with schema (websiteId, startAt, endAt, eventName) and handler that calls Umami API GET /api/websites/{websiteId}/event-data/stats
    server.tool(
      "get_event_data_stats",
      "Get event data statistics (summary counts) for a website",
      {
        websiteId: z.string().describe("Website UUID"),
        startAt: z.number().describe("Start timestamp in milliseconds"),
        endAt: z.number().describe("End timestamp in milliseconds"),
        eventName: z.string().optional().describe("Filter by event name"),
      },
      async ({ websiteId, startAt, endAt, eventName }) => {
        const data = await client.call(
          "GET",
          `/api/websites/${websiteId}/event-data/stats`,
          undefined,
          { startAt, endAt, eventName }
        );
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the purpose and does not disclose behavioral traits like read-only nature, potential side effects, or any required permissions. The agent lacks safety context beyond the tool's name.

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?

The description is a single sentence, concise and front-loaded with the key purpose. However, it is minimal, lacking any structural elements like bullet points or additional context, which prevents a perfect score.

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

Completeness2/5

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

Given the tool has 4 parameters, no output schema, and numerous sibling tools with overlapping purposes, the description is too sparse. It does not explain return format, the role of required timestamps, or how this tool fits relative to others like get_event_data_events or get_stats.

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 the schema already fully documents parameters. The description adds no additional meaning or context about the parameters beyond the high-level purpose, so baseline 3 is appropriate.

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?

The description clearly states 'Get event data statistics (summary counts) for a website', using a specific verb and resource. Among siblings like get_event_data_events, get_event_data_fields, and get_event_data_values, this distinguishes itself by specifying 'statistics' and clarifying it provides summary counts.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools such as get_stats, get_event_series, and get_session_stats, the agent has no criteria to differentiate usage contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/umami-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server