Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_website

Modify an existing Umami website's configuration, including its name, domain, share ID, and session replay or heatmap settings. Use it to adjust analytics tracking options for a specific site.

Instructions

Update an existing website's configuration

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>"
    },
    "name": "update_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name
domainNoNew domain
shareIdNoShare ID (set to null to remove)
websiteIdYesWebsite UUID
replayConfigNoSession replay and heatmap collection settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • addedInput schema / properties / replayConfig
      Added value: +{
+  "additionalProperties": false,
+  "description": "Session replay and heatmap collection settings",
+  "properties": {
+    "blockSelector": {
+      "type": "string"
+    },
+    "heatmapEnabled": {
+      "type": "boolean"
+    },
+    "heatmapSampleRate": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "maskLevel": {
+      "enum": [
+        "strict",
+        "moderate"
+      ],
+      "type": "string"
+    },
+    "maxDuration": {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    },
+    "replayEnabled": {
+      "type": "boolean"
+    },
+    "sampleRate": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / properties / shareId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. First observedv1.2.1

TDQS

C2.9/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 does not explain whether the update is partial or full, whether omitted fields remain unchanged, what permissions are required, or what happens when nested replayConfig values are modified.

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 front-loaded sentence with no filler. It is appropriately concise, though its brevity contributes to the lack of behavioral and usage detail elsewhere.

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?

For a mutation tool with a nested replayConfig object, no annotations, and no output schema, the description is too thin. It does not cover update semantics, permission requirements, or the effect of modifying replay and heatmap settings.

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 documents the five parameters, including the nested replayConfig settings. The description adds no parameter-level meaning beyond the schema, which is acceptable at the baseline of 3 when the schema does the heavy lifting.

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 states a specific verb and resource: update an existing website's configuration. It is clear enough for an agent to identify the operation, but it does not distinguish this from sibling website-management tools such as update_share, reset_website, or delete_website.

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 alternatives, no prerequisites, and no exclusions. The only implied usage is that the website already exists.

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