Skip to main content
Glama

Create an invite link

members_create_invite_link

Create a shareable invite link for this space; share the returned url with the people who should join.

POST /api/v1/members/invite-links

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). Give the returned url to the user to share; anyone holding it can join until it is revoked, expires, or runs out of uses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
roleNomember
teamIdNo
maxUsesNo
expiresAtNo
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.
requiresApprovalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations, which only say it is not read-only, not destructive, and closed-world. The description discloses the required permission level (owner or admin), the key tier needed per role (write-level for member, manage-level for admin, with a 403 explaining which), and the security lifetime of the link ('anyone holding it can join until it is revoked, expires, or runs out of uses').

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 the output, then layers prerequisites and caveats. Slight waste in the raw 'POST /api/v1/members/invite-links' line and in restating the url hand-off twice ('share the returned url' and 'Give the returned url to the user to share').

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 six-parameter mutation with no output schema, the description covers the essential operational facts: auth/space selection, permission tiers, and link lifetime, and it names the returned field so the missing output schema does not hurt. The two undocumented parameters (teamId, requiresApproval) are the only real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at only 17%, the description compensates substantially: it explains targetSpaceId usage, ties role to required key level, and implies the meaning of maxUses ('runs out of uses') and expiresAt ('expires'). teamId and requiresApproval remain undocumented in both schema and description, which keeps it short of a 5.

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 ('Create a shareable invite link for this space') and explains the artifact produced ('the returned url'). It is distinguishable from siblings like members_revoke_invite_link by the create framing, but it never contrasts with members_invite (presumably email-based invitation), leaving that distinction to 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 concrete preconditions and context: for multi-space accounts call auth_verify first, ask the user which space, and pass targetSpaceId, plus 'Manage members only when the user asks.' What is missing is any statement of when to prefer this over members_invite or when a link is inappropriate.

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.