Skip to main content
Glama

mcp-notion__notion-get-teams

Read-onlyIdempotent

Retrieves a list of teams (teamspaces) in the current workspace. Shows which teams exist, user membership status, IDs, names, and roles.

Teams are returned split by membership status and limited to a maximum of 10 results.

  1. Search for teams by name: {"query": "engineering"}

  2. Find a specific team: {"query": "Product Design"} Through Royally: its server marks it read-only, so it runs straight away.

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": "mcp-notion__notion-get-teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search query to filter teams by name (case-insensitive).
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real behavioral context beyond the annotations: results are split by membership status, carry IDs, names, and roles, and are capped at a maximum of 10 per membership type. That result-limit disclosure is exactly the kind of operational fact an agent needs before deciding whether to paginate or refine a query. It stops short of saying how to retrieve more than 10 results, which is a meaningful omission for a listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences and the examples are front-loaded and useful, but the trailing fragment 'Through Royally: its server marks it read-only, so it runs straight away' is garbled, redundant with the readOnlyHint annotation, and adds noise at the end of an otherwise clean definition. Removing it would make the description tighter and less confusing.

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 read-only listing tool with no required parameters, no output schema, and full schema coverage, the description covers purpose, filtering, result shape, and the 10-item cap well. The one remaining gap is what an agent should do when the cap is reached, since no pagination or continuation mechanism is mentioned.

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 every parameter is already documented in the schema, which sets the baseline at 3. The examples add some flavor for `query` (it accepts names such as 'engineering' or 'Product Design'), but they add no meaning beyond the schema. The `skill`, `site_id`, and `instructions_version` parameters are not addressed in the description at all.

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 opens with a specific verb and resource: 'Retrieves a list of teams (teamspaces) in the current workspace,' and immediately clarifies that 'teams' means 'teamspaces.' That synonym disambiguates it from siblings such as notion-get-groups and notion-get-users, but the description never names those siblings, so the differentiation is implicit rather than explicit.

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 three worked examples clearly establish when to use this tool: a bare call to list everything, a query to search by name, and a query to find one specific team by name. That gives an agent enough context to choose the tool. There is no guidance on when NOT to use it, such as when listing members of a single team would be better served by another tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources