Skip to main content
Glama

List invite links

appInvitesList
Read-onlyIdempotent

List the invite links on one owned private app, newest first, each with what it is doing. Read private first: the links only let anyone in while the app is Private AND live on Tofu’s static hosting, so on a public app they open nothing. state is active (it can still let ONE person in), redeemed (someone opened it — the first time a link is opened it admits that person and stops working for anyone else) or expired (nobody used it before its date). url is the shareable link itself, shown only while the link is active; expiresAt is when it stops working by itself, and createdAt is null for a redeemed link because Tofu keeps only its expiry once it is used. A person who opened a link keeps their pass for up to 30 days whatever happens to the link after. It writes nothing, and no field but a live link’s own url ever carries the secret.

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": {
      "projectId": "<projectId>"
    },
    "name": "appInvitesList"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
invitesYes
messageYes
privateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond them: the Private-plus-hosting precondition for links to work at all, the 30-day pass persistence for redeemers, and the security disclosure that only a live link's own `url` carries the secret.

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?

The action and scope are front-loaded in the first clause and no sentence is pure filler. The paragraph is long and enumerates state values that the output schema likely already documents, and its single-block structure makes it denser than necessary.

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 one-parameter read tool with an output schema and full annotations, this is nearly complete: it covers preconditions, state meanings, field behavior and a secret-exposure guarantee. It stops short of stating result volume, pagination, or behavior when the app is not owned by the caller.

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?

Only one parameter (projectId) exists at 0% schema description coverage, so the description must carry the burden. 'On one owned private app' implies projectId selects the app and must be owned by the caller, but the parameter is never named or characterized directly, leaving the mapping to inference.

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 — 'List the invite links on one owned private app, newest first' — including ordering and scope. It distinguishes itself from the mutating siblings (appInvitesCreate, appInvitesRevoke) through the verb and 'writes nothing', though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real prerequisite — 'Read `private` first' — and explains that links only admit people while the app is Private and live on static hosting, which tells the agent when the output is meaningful. However, there is no explicit when-to-use/when-not guidance or routing to alternatives such as create/revoke.

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