team.members.deleteRemove a team member.
| Name | Required | Description | Default |
|---|---|---|---|
| memberId | Yes | Member ID |
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | ||
| http_status | Yes | HTTP status of the API response |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely paraphrases the title and adds no behavioral detail beyond what the annotations already provide. It does not explain consequences such as irreversibility, cascading effects on related resources, or required authorization, though it does not contradict the destructiveHint annotation.
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?
The description is one short, front-loaded sentence with no wasted words. It is concise, though it borders on simply restating the title.
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?
For a destructive, non-idempotent mutation, the definition is too thin. It does not state whether removal is permanent, what happens to related team invitations or memberships, or what prerequisites must hold before calling the tool. The annotations and schema cover only the basic safety and input details.
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?
The schema has 100% coverage for the single parameter, describing memberId as 'Member ID'. The description adds no additional meaning about where to obtain the ID or what form it takes, so the baseline score of 3 is appropriate.
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?
The description states a clear action ('Remove') and resource ('a team member'), so an agent can immediately tell what the tool operates on. It does not explicitly distinguish this from the many sibling delete tools, but the resource is specific enough to avoid confusion.
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?
There is no guidance about when to use this tool versus alternatives such as team.members.add, archived.delete, or other delete tools. The intended usage is only implied by the wording and is not supported by any context, exclusions, or prerequisites.
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.
The resource namespaces make most tools easy to tell apart, and each action has a clear target. A couple of boundary cases exist, such as attachments.add versus mails.inject, since both relate to putting files on a simulated email, but descriptions mostly resolve the ambiguity.
Every tool follows the same resource.action convention, and the action verbs are predictable across the set, including delete_bulk and rotate_secret. The pattern is uniform even across different resource families, making the API very predictable.
With 40 tools, the surface is quite large for an MCP server, even though the namespaces are clean. Many singular and bulk delete variants could be combined or expressed as parameters to reduce the count, so the set feels heavier than it needs to be.
The server covers the main lifecycle needs for mailboxes, emails, attachments, archived mailboxes, domains, identities, OAuth clients, and team management. Minor gaps remain, such as no mailbox update/rename, no manual archive action, and no invitation acceptance endpoint, but agents can work around these.