Skip to main content
Glama

Just List

Get an invite link for a list

share_link
Idempotent

Make an invite link for one of the user's own lists. Anyone who opens it can join the list and edit it with them. Only for lists the user created.

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": {
      "listId": "<listId>"
    },
    "name": "share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list's id (listId from list_my_lists, create_list or write_list_with_justy)

Output Schema

NameRequiredDescriptionDefault
urlNo
titleNo
statusYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive and open-world behavior, so the bar is lower; the description adds the important consequence that anyone with the link "can join the list and edit it with them", which is the security-relevant fact an agent must weigh before sharing. It stops short of covering link expiry, revocation, or whether repeated calls return the same URL.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, followed by the effect and then the restriction. No filler or restatement of the title beyond what carries meaning.

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?

With one fully documented parameter, an output schema handling return values, and annotations covering the safety profile, the description covers nearly everything an agent needs. The remaining gap is lifecycle detail about the generated link (persistence, expiry), which is a minor omission for a low-complexity tool.

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 description coverage is 100% and the single listId parameter is already documented with its source tools (list_my_lists, create_list, write_list_with_justy). The description adds no format or sourcing detail beyond that, so the baseline of 3 applies.

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?

"Make an invite link for one of the user's own lists" gives a specific verb (make) and resource (invite link for a list), and the ownership qualifier separates it from generic list readers like get_list or create_list. An agent can tell immediately what the call produces 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?

The description states the precondition clearly ("Only for lists the user created"), which is the main eligibility gate an agent needs before calling. It does not name an alternative tool for lists the user doesn't own, nor does it say what to do on failure, so it falls short of full when/when-not routing.

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