Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_event

Track custom events or pageviews server-side by sending them to Umami with required website, hostname, and URL details.

Instructions

Send a custom event or pageview to Umami (useful for server-side tracking)

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": {
      "websiteId": "<websiteId>",
      "hostname": "<hostname>",
      "url": "<url>"
    },
    "name": "send_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoClient IP for trusted server-side collection
tagNoEvent tag
urlYesURL path (e.g. '/checkout')
titleNoPage title
screenNoScreen dimensions (e.g. 1920x1080)
hostnameYesHostname of the site (e.g. 'example.com')
languageNoBrowser language (e.g. 'en-US')
referrerNoReferrer URL
eventDataNoCustom event data as key-value pairs
eventNameNoCustom event name (omit for pageview)
timestampNoUnix timestamp in seconds
userAgentNoClient user agent
websiteIdYesWebsite UUID (used as the 'website' field in payload)
distinctIdNoStable user identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.1
    • addedInput schema / properties / distinctId
      Added value: +{
+  "description": "Stable user identifier",
+  "type": "string"
+}
    • addedInput schema / properties / ip
      Added value: +{
+  "description": "Client IP for trusted server-side collection",
+  "type": "string"
+}
    • addedInput schema / properties / screen
      Added value: +{
+  "description": "Screen dimensions (e.g. 1920x1080)",
+  "type": "string"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Event tag",
+  "type": "string"
+}
    • addedInput schema / properties / timestamp
      Added value: +{
+  "description": "Unix timestamp in seconds",
+  "type": "integer"
+}
    • addedInput schema / properties / userAgent
      Added value: +{
+  "description": "Client user agent",
+  "type": "string"
+}
  2. First observedv1.2.1

TDQS

B3.1/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 burden. It never discloses that this is a write operation against a live analytics dataset, whether events are deduplicated or timestamp-normalized, whether authentication is required, what rate limits apply, or what the call returns on success/failure. For a 14-parameter ingestion endpoint, this is a serious omission.

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?

A single front-loaded sentence with zero filler. It is efficiently written, though the brevity doubles as under-specification for a tool with this many parameters.

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 14 parameters, a nested object (eventData), no annotations, and no output schema, the description is far too thin. An agent gets no guidance on which of the three required fields drive routing, how eventName vs pageview affects payload interpretation, or what a successful response looks like.

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 every one of the 14 parameters already has an inline description (e.g. 'omit for pageview', 'Website UUID'). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb ('Send') and resource ('custom event or pageview') and names the target platform (Umami). It does not distinguish itself from nearby write-path siblings like batch_events, send_identify, send_performance, or send_link_or_pixel_event, so an agent cannot fully separate them from the description alone.

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?

"Useful for server-side tracking" implies the context (backend-originated ingestion rather than browser-instrumented collection), which is a real usage hint. But there is no statement of when to prefer batch_events for multiple events, no prerequisites about API credentials, and no exclusions.

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

Deploy Server

Other Tools