umami-mcp

get_my_teams

Retrieves the list of teams the current user belongs to, with pagination, sorting, and page size options for team management.

Instructions

Get the list of teams the current user belongs to

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_teams"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`orderBy`	No	Sort field
`pageSize`	No	Results per page
`sortDescending`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / orderBy

Added value: +{
+  "description": "Sort field",
+  "type": "string"
+}

removedInput schema / properties / query

Removed value: -{
-  "description": "Search query to filter teams",
-  "type": "string"
-}

addedInput schema / properties / sortDescending
```
Added value: +{
+  "type": "boolean"
+}
```

First observedv1.2.1Mar 19, 2026

TDQS

A3.8/5.0

Behavior3/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 burden. It implies a read-only list scoped to the current user, but does not disclose pagination behavior, permission requirements, return format, or whether all memberships are included. The core read semantics are clear, but important behavioral context is missing.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and scope.

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?

For a simple read-only list tool with four optional parameters and no output schema, the description gives enough context to call it correctly. It could say more about the returned team representation, but the low complexity keeps this from being a major 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 description coverage is 75%, with page, orderBy, and pageSize documented while sortDescending has no schema description. The tool description provides no additional parameter meaning, so the schema does most of the work; baseline 3 is appropriate for this coverage level.

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 states a specific verb (Get), resource (list of teams), and scope (the current user belongs to). This clearly distinguishes it from siblings like list_teams or get_user_teams, which operate on broader or specified users.

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 phrase 'current user belongs to' implies when to use this tool, but it does not explicitly say when to prefer it over siblings such as list_teams or get_user_teams. There are no exclusions or alternative-routing instructions.

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

Deploy Server