Skip to main content
Glama

List Invitations

list_invitations
Read-onlyIdempotent

List the invitations that include the workspace (the current one unless workspaceId names another), newest first, whatever their status. Returns { invitations, total, hasMore }. Page with offset while hasMore is true. Needs the members.manage permission, which Admin holds.

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": "list_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoInvitations per page
offsetNoInvitations to skip; increase by limit while hasMore is true
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
resultYesAn object with invitations, total (count of all invitations) and hasMore. Each item is one invitation. The 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.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit by adding what they cannot: newest-first ordering, no status filtering, the required members.manage permission and who holds it, and the pagination loop condition tied to hasMore. Those are exactly the facts an agent needs before calling or looping.

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 scope and ordering in the first sentence, then return shape, paging, and permission in descending order of importance. Slightly dense with nested parentheses, but every clause carries information and nothing is padding.

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?

For a three-optional-parameter read tool with an output schema, the description covers scope, ordering, filtering behavior, pagination strategy, authorization, and the return fields. The return-shape sentence is mildly redundant with the output schema but harmless as a quick orientation.

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% and the schema already explains limit as page size, offset as skip-until-hasMore, and workspaceId as coming from list_workspaces with a current-workspace default. The description restates the paging loop and the current-workspace default, adding reinforcement but little genuinely new meaning beyond the structured fields.

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 ("List the invitations") and narrows scope precisely: invitations that include the workspace, the current one unless workspaceId overrides, newest first, regardless of status. That parenthetical scope and the "whatever their status" clause let an agent distinguish this from any status-filtered or user-scoped listing without opening the schema.

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 when-to-use conditions: omit workspaceId to act in the current workspace, page with offset while hasMore is true, and the caller must hold members.manage (Admin does). It does not name an alternative tool or an explicit when-not-to-use case, but no sibling in the catalog covers invitations, so the omission is minor.

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