Skip to main content
Glama

mcp-notion__notion-get-groups

Read-onlyIdempotent

Retrieves permission groups in the current workspace that you can see, with their IDs and names.

People properties reference a group as space_permission_group-<id>. Use this tool to find the name of a group in a People property value, or to find a group by name before setting it in a People property.

Listings are sorted by name and searches return the closest matches first. Results are limited to a maximum of 25 groups.

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

  2. Look up a group from a People property value: {"query": "space_permission_group-141083e9-5e66-4c8f-8a38-bce5762903c2"} 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-groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional group name to search for (case-insensitive), or a group ID from a People property value (`space_permission_group-<id>` or the bare ID) to look up that group.
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the prose. The description does add genuinely new behavior, namely that listings are sorted by name, searches return closest matches first, and results are capped at 25 groups, but it omits anything about pagination or how to retrieve groups beyond that cap, which matters for a capped list 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 body is front-loaded and the worked examples are compact and useful. However, the trailing fragment "Through Royally: its server marks it read-only, so it runs straight away" is garbled, reads like injected noise, and repeats safety information the annotations already carry, so it dilutes an otherwise tight definition.

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 four-parameter, zero-required lookup tool with no output schema, the description covers what it returns (IDs and names), the ordering, the result cap, and the reference format needed to round-trip a People property value. The only real gap is behavior for workspaces exceeding the 25-group limit.

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, and the description earns an increment by tying the `query` parameter to the `space_permission_group-<id>` People property format and demonstrating both the name and ID lookup modes in examples 2 and 3. The remaining parameters (skill, site_id, instructions_version) are plumbing already documented in the schema, and the description rightly does not restate them.

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 names a specific verb and resource ("Retrieves permission groups in the current workspace") plus the returned fields (IDs and names) and the visibility scope ("that you can see"). It never distinguishes itself from look-alike siblings such as notion-get-users or notion-get-teams, so it stops short of full sibling differentiation.

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?

It gives two concrete when-to-use triggers: resolving a group name from a People property value, and finding a group by name before writing it into a People property. The three examples reinforce those cases, but there is no explicit when-not guidance or named alternative for adjacent lookups (users, teams).

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