Skip to main content
Glama

Revoke an invite link

members_revoke_invite_link
Destructive

Revoke an invite link so nobody new can join through it.

DELETE /api/v1/members/invite-links/{inviteLinkId}

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": {
      "inviteLinkId": "<inviteLinkId>"
    },
    "name": "members_revoke_invite_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteLinkIdYes
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

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and readOnly=false, so the mutation profile is covered. The description adds real context beyond them: the permission ceiling (owner/admin), the distinction between write-level keys for the member role versus manage-level keys for admin, and the 403-as-diagnostic behavior. It stops short of saying whether a revoked link can be restored or what happens to members already invited through it.

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-loaded with the effect, then the endpoint, then the multi-space workflow, then the permission model — a sensible ordering. The raw HTTP line is low-value for an agent but takes only one line; the permission sentence is dense but each clause carries distinct information.

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?

With only two parameters, a boolean-returning destructive operation, and no output schema, the definition covers the essentials: what is destroyed, what permissions and key levels are needed, how errors signal the fix, and how to resolve the space. The single remaining gap, sourcing inviteLinkId, is minor for a tool of this complexity.

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 already documents the auth_verify/ask-the-user flow in the schema itself, so the description largely repeats it. inviteLinkId has no schema description and the definition does not say where to obtain a valid id (presumably members_list_invite_links) or its format, leaving the required parameter under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Revoke an invite link') plus the concrete outcome ('so nobody new can join through it'), which is exactly the effect-level distinction an agent needs versus create/list invite-link tools. The DELETE endpoint path removes any ambiguity about the operation type.

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 explicit when-to-use scoping ('Manage members only when the user asks') and a multi-space prerequisite flow (call auth_verify, ask the user, pass targetSpaceId). It does not name sibling alternatives such as members_list_invite_links or members_cancel_invitation, so the agent must infer where to get the id and which sibling handles cancellation.

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.