umami-mcp

update_team

Modify a team's name or access code in Umami Analytics by specifying the team UUID and the fields to change.

Instructions

Update a team's name or access code

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": {
      "teamId": "<teamId>"
    },
    "name": "update_team"
  }
}

Input Schema

Name	Required	Description
`name`	No	New team name
`teamId`	Yes	Team UUID
`accessCode`	No	New access code

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / accessCode

Added value: +{
+  "description": "New access code",
+  "maxLength": 50,
+  "type": "string"
+}

addedInput schema / properties / name / maxLength
```
Added value: +50
```
addedInput schema / properties / teamId / format
```
Added value: +"uuid"
```

changedInput schema / required

Previous value: -[
-  "teamId",
-  "name"
-]New value: +[
+  "teamId"
+]

First observedv1.2.1Mar 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It doesn't disclose whether the update is partial or requires specific permissions, whether changes are reversible, or what happens if only one field is provided. This is a mutation tool, so these omissions are significant.

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?

A single, front-loaded sentence with no wasted words. It is appropriately sized for a simple update tool.

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?

Given the low complexity (3 params) and full schema coverage, the description provides the basic purpose but fails to cover behavioral aspects like permissions or partial update semantics. Without annotations, more context would be expected for a mutation tool, leaving a moderate gap.

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 each parameter is already documented. The description adds marginal value by naming the two updatable fields, but doesn't provide format, constraints, or behavior 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (update) and resource (team's name or access code), clearly distinguishing it from create_team, delete_team, and update_team_user. However, it doesn't explicitly mention the required teamId parameter or name a sibling alternative for clarity.

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?

No guidance is given on when to use this tool versus alternatives like update_team_user or create_team. The description merely states the action without any context about prerequisites or scenarios, leaving usage entirely implied.

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

Deploy Server