Skip to main content
Glama
arttus

umami-mcp-server

by arttus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get team details and members

umami_get_team
Read-onlyIdempotent

Retrieve a team's details, including full member list and roles, by providing its team ID. Choose markdown or JSON output.

Instructions

Get a team's details, including its full member list and roles.

Args:

  • team_id (string, required): Team UUID. Get this from umami_list_teams.

  • response_format ('markdown' | 'json'): Output format (default: 'markdown').

Returns: JSON shape: { "id": string, "name": string, "access_code": string, "members": [ { "user_id": string, "username": string, "role": string } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYesTeam UUID.
response_formatNoOutput format: 'markdown' for a readable summary, 'json' for raw structured data.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly/idempotent/non-destructive, so the bar is lower. The description adds useful behavioral detail: it returns the full member list with roles, supports markdown/json output, and gives the exact JSON shape. This goes meaningfully beyond the annotations.

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 compact, front-loaded, and structured with Args and Returns sections. Every sentence adds useful information with no filler or redundancy.

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

Completeness4/5

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

There is no output schema, so the description compensates by including the JSON return shape. Combined with clear parameter guidance and comprehensive annotations, the description is sufficiently complete for a simple read-only tool, though it could explicitly mention sibling distinctions.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds the valuable guidance that team_id should come from umami_list_teams, which helps the agent construct a valid call. response_format semantics are already covered by the schema, but the added source guidance justifies a 4.

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 ('Get') and resource ('team'), and specifies the key content: details, full member list, and roles. This clearly distinguishes it from siblings like umami_list_teams (listing teams) and umami_get_team_websites (team websites).

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 description implies usage for fetching team details/members and tells the agent to obtain team_id from umami_list_teams, but it does not explicitly state when to choose this tool over alternatives or mention exclusions such as 'for team websites use umami_get_team_websites'.

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