list_usersList all team members on the account
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (0-indexed) | |
| limit | No | Results per page, 1-100 (default 20) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | One row per team member — id, email, fullname, role, avatar_url, the clients they can reach, and invite_pending while they have not accepted yet. | |
| meta | No | Page, limit and total row count. | |
| success | Yes | True when the call succeeded. |
Changes observed during successful MCP inspections.
Input schema / properties / limit / descriptionPrevious value: -"Results per page"New value: +"Results per page, 1-100 (default 20)"Input schema / properties / limit / maximumAdded value: +100Input schema / properties / limit / minimumAdded value: +1Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / properties / meta / descriptionPrevious value: -"Pagination for the list — page, limit and the total row count."New value: +"Page, limit and total row count."Output schema / properties / meta / properties / limit / descriptionPrevious value: -"Maximum rows per page."New value: +"Max rows per page."Output schema / properties / meta / properties / page / descriptionPrevious value: -"Zero-based index of the page returned."New value: +"Page index, zero-based."Output schema / properties / meta / properties / total / descriptionPrevious value: -"Total rows matching the query across all pages."New value: +"Total rows matching the query."Output schema / properties / success / descriptionPrevious value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "description": "One row per team member — id, email, fullname, role, avatar_url, the clients they can reach, and invite_pending while they have not accepted yet.",
+ "items": {},
+ "type": "array"
+ },
+ "meta": {
+ "additionalProperties": true,
+ "description": "Pagination for the list — page, limit and the total row count.",
+ "properties": {
+ "limit": {
+ "description": "Maximum rows per page.",
+ "type": "number"
+ },
+ "page": {
+ "description": "Zero-based index of the page returned.",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total rows matching the query across all pages.",
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the account-scoping fact ('on the account') and says nothing about pagination behavior or whether the result set is paginated despite the page/limit params.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with no filler. It is appropriately sized, though the terseness leaves the tool with almost no guidance content to front-load.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and annotations cover the safety profile, so return values and mutation risk need not be described. Still, for a listing tool with pagination, the description omits any hint about result scope or paging, leaving a small but real gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so page and limit are fully documented in the schema with defaults and bounds. The description adds no additional parameter meaning, which meets the baseline for high-coverage schemas.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List all team members'), which is unambiguous on its own. However, it does not differentiate from related siblings like get_current_user, whoami, or the other list_* tools, which an agent must disambiguate without help.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this versus get_current_user, whoami, or count_clients-style alternatives, and no prerequisites or exclusions given. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.