umami-mcp

batch_events

Send multiple events or pageviews in one request to reduce network calls when collecting Umami Analytics data.

Instructions

Send multiple events or pageviews in a single batch request

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": {
      "events": "<events>"
    },
    "name": "batch_events"
  }
}

Input Schema

Name	Required	Description	Default
`events`	Yes	Array of events to send

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2.1.1Oct 24, 2026
- addedInput schema / properties / events / items / properties / distinctId
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / events / items / properties / ip
```
Added value: +{
+  "description": "Client IP for trusted server-side collection",
+  "type": "string"
+}
```
- addedInput schema / properties / events / items / properties / screen
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / events / items / properties / tag
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / events / items / properties / timestamp
```
Added value: +{
+  "description": "Unix timestamp in seconds",
+  "type": "integer"
+}
```
- addedInput schema / properties / events / items / properties / userAgent
```
Added value: +{
+  "description": "Client user agent",
+  "type": "string"
+}
```
- addedInput schema / properties / events / maxItems
```
Added value: +500
```
- addedInput schema / properties / events / minItems
```
Added value: +1
```
First observedv1.2.1Mar 19, 2026

TDQS

A3.5/5.0

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 behavioral-disclosure burden. It states the operation but omits authentication requirements, partial-failure behavior, idempotency, rate limits, and response format for a write/ingestion tool.

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?

The description is a single front-loaded sentence with no filler. It states the core operation efficiently.

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?

The schema is rich, including nested event fields and batch size constraints, which supports basic invocation. However, with no annotations and no output schema, the description should do more to explain batch response or partial-success behavior, leaving a meaningful gap for an ingestion tool.

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%, so the detailed nested event fields and min/max item limits are already documented in the schema. The description does not add parameter meaning beyond the schema, 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 uses a specific verb ('Send') and states the exact resource/scope: multiple events or pageviews in one batch request. The words 'multiple' and 'batch' distinguish it from the single-event sibling send_event without requiring the schema to be opened.

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?

The batching context implies when to use this tool rather than send_event, but there is no explicit alternative named, no exclusion criteria, and no prerequisites. Usage is inferable but not documented.

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

Deploy Server