Skip to main content
Glama

List active invite links

members_list_invite_links
Read-only

Invite links of this space that have not been revoked, each with its url.

GET /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).

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_list_invite_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/non-open-world, and the description adds genuinely useful context beyond them: caller must be an owner or admin, and a 403 reports which key level is missing. It also states what is returned (each link's url). The mutation-oriented lines ("a write-level key can grant the member role") read as copy-paste from a different tool and blur the read-only profile rather than contradicting it.

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

Conciseness3/5

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

The opening sentence and endpoint line are front-loaded and efficient, but the second paragraph bundles space-selection guidance, member-management policy, and write-key/member-role rules that do not belong to a read-only listing tool. Several sentences do not earn their place for this operation.

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 single-parameter read tool with annotations and full schema coverage, the description covers the essentials: what is returned, permission requirements, and multi-space handling. Only the pagination/size of the result set is unaddressed, and the leftover mutation guidance adds noise rather than filling a real gap.

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?

With one parameter at 100% schema coverage, the schema already fully documents targetSpaceId, including the auth_verify/ask-the-user instruction. The description restates that same guidance and adds no new syntax or format detail, so the 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?

"Invite links of this space that have not been revoked, each with its `url`" names the resource and a precise scope filter (non-revoked), which separates it from members_list_invitations and members_revoke_invite_link. The listing verb is only implied by the title rather than stated in the description, so it stops short of a 5.

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 prerequisites and routing: for multi-space accounts call auth_verify, ask the user which space, then pass targetSpaceId. It also sets a guardrail ("Manage members only when the user asks"), but never explicitly contrasts this tool with the sibling list tools such as members_list_invitations.

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.