Skip to main content
Glama

Cancel an email invitation

members_cancel_invitation
Destructive

Cancel a pending email invitation so its link stops working.

DELETE /api/v1/members/invitations/{invitationId}

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. Manage members only when the user asks. Requires the user to be an owner or admin of the space; a write-level key can grant the member role, and admin needs a manage-level key (a 403 says which).

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": {
      "invitationId": "<invitationId>"
    },
    "name": "members_cancel_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
invitationIdYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructive=true/readOnly=false, and the description adds material context on top: the concrete effect of breaking the invite link, the exact endpoint, and the permission model (owner/admin required, write-level vs manage-level key, 403 disclosing which is missing). It does not cover idempotency or behavior on non-pending invitations, but the added auth/effect detail clearly exceeds annotation coverage.

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 purpose, then endpoint, then scoping/permission rules — a logical order for an agent to read. The permission sentence ('a write-level key can grant the member role, and admin needs a manage-level key') is dense and slightly ambiguous but carries information rather than filler.

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 two-parameter destructive mutation with no output schema, the definition covers effect, auth level, error signal (403), and multi-space scoping — most of what an agent needs. Remaining gaps (behavior on already-accepted or expired invitations, whether repeated calls are safe) are minor but real for a destructive operation.

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 50%: targetSpaceId is documented in both schema and description, and the description adds conditional guidance (multi-space → auth_verify → ask user) beyond the schema's plain 'call auth_verify first'. invitationId is undocumented in both places except implicitly via the URL path template, so compensation for the coverage gap is only partial.

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 and resource ('Cancel a pending email invitation') plus the observable effect ('its link stops working'), and the endpoint path confirms it deletes an invitation by id. It does not explicitly contrast with members_revoke_invite_link or members_list_invitations, so an agent must infer the invitation-vs-link distinction from the resource wording alone.

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 usage context: only act when the user asks, and for multi-space accounts call auth_verify and ask which space before passing targetSpaceId. It stops short of explicit exclusions (e.g., when to use revoke_invite_link instead, or what to do if the invitation is already accepted/expired).

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.