Skip to main content
Glama

Revoke Invitation

revoke_invitation
DestructiveIdempotent

Revoke a pending invitation that includes the workspace (the current one unless workspaceId names another), so its link stops working. Confirm with the user first, naming the email it was sent to. Only the owner may revoke an invitation for an organization admin. Needs the members.manage permission, which Admin holds. Fails with 404 when no such invitation includes this workspace, and with 400 when it is no longer pending. Returns the invitation with status revoked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesInvitation id from list_invitations or send_invitation
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesThe invitation: id, email, organizationId, organizationRole, status (pending, accepted, expired or revoked), workspaces [{ workspaceId, workspaceName, role }], expiresAt and createdAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/not-readOnly/idempotent) by disclosing the authorization model, the required permission, the confirmation protocol, and the exact failure semantics (404 when no invitation includes this workspace, 400 when no longer pending). This is exactly the operational context annotations cannot carry.

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

Conciseness4/5

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

Front-loads the action and effect, then layers preconditions, permissions, and error codes in a logical order with no filler. A few sentences are dense run-ons (the owner/org-admin clause), which slightly hurts readability but not efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return detail need not be spelled out, yet the description still states the result ('returns the invitation with status revoked'). Combined with permission requirements, confirmation guidance, and error codes, nothing an agent needs to invoke this destructive tool correctly is missing.

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 coverage is 100%, so both id and workspaceId are already documented in the schema, including the default-to-current-workspace behavior and the id-consistency rule. The description only restates the workspace default and adds nothing new about parameter formats or values; baseline 3 applies.

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?

States a specific verb+resource ('Revoke a pending invitation') plus the workspace scope and the effect ('its link stops working'). It is clearly distinct from send_invitation in intent, but it never explicitly names the sibling it should be chosen over (e.g. revoke_connect_link), so routing relies on the agent's own inference.

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?

Gives real preconditions: confirm with the user first, only the owner may revoke for an org admin, and members.manage permission is required. It stops short of naming alternatives, so an agent must decide on its own between this and revoke_connect_link.

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