Skip to main content
Glama
arttus

umami-mcp-server

by arttus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a website in Umami

umami_create_website

Register a new website in Umami to receive a website ID and tracking snippet, enabling analytics for any client or project.

Instructions

Register a new website for tracking in Umami. This is the first step in onboarding a client or project: it returns a website ID that goes into the tracking script, and that every stats tool in this server uses.

Args:

  • name (string, required): Display name for the website.

  • domain (string, required): The domain being tracked, e.g. 'example.com'. No protocol.

  • team_id (string, optional): Create the website under a team instead of your personal account. Use umami_list_teams to find the ID.

  • id (string, optional): Force a specific UUID for the website, for example to match an ID reserved elsewhere.

Returns: JSON shape: { "id": string, "name": string, "domain": string, "team_id": string | null, "created_at": string, "tracking_snippet": string }

Examples:

  • "Set up tracking for the new client site" -> name="Walker's Land Services", domain="walkerslandservices.com"

  • "Add this under the Gradeline team" -> name="Gradeline", domain="gradeline.info", team_id=""

Error handling:

  • Fails if a website with the same forced 'id' already exists.

  • Not available on Umami Cloud in read-only API-key mode without appropriate account permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoForce a specific UUID for the website.
nameYesDisplay name for the website.
domainYesDomain being tracked, e.g. 'example.com'. No protocol or path.
team_idNoCreate under this team instead of your personal account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses meaningful behavior: it returns a tracking snippet and website ID, fails on duplicate forced IDs, and is unavailable in read-only API-key mode on Umami Cloud. This gives the agent a realistic model of side effects and failure conditions.

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 well-structured with clear sections for Args, Returns, Examples, and Error handling. The opening sentence front-loads the core purpose and the rest is tightly scoped with no filler. Every section earns its place.

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

Completeness5/5

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

Given the tool has no output schema, the description supplies the full return JSON shape, highlights the tracking ID's role, and covers the main error cases. It gives enough context for an agent to call the tool correctly and interpret the result.

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

Parameters5/5

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

Even though the schema covers all parameters, the description adds practical semantics: team_id is tied to umami_list_teams, id is explained with a use case ('match an ID reserved elsewhere'), and domain's 'No protocol' constraint is reinforced. The examples map natural language requests to actual parameter values, which is genuinely helpful.

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 opens with a specific verb and resource — 'Register a new website for tracking in Umami' — and immediately clarifies the tool's role as the first step in onboarding a client or project. It explains the returned website ID feeds into the tracking script, which distinguishes it from sibling tools like umami_update_website or umami_list_websites.

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

Usage Guidelines4/5

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

The description gives clear context for when to use it: it is the first step in onboarding and must precede use of stats tools. It also cross-references umami_list_teams to find a team_id. However, it does not explicitly name alternatives or state when not to use it, such as 'use umami_update_website for existing sites.'

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