Skip to main content
Glama

List saved lists

list_user_lists
Read-onlyIdempotent

Named lists on this account, including Saved (isDefault=true) and lists the team shares. Each row has name, alreadyOnThis or projectCount, and source. An alert and its companion list are the same match set: every match except dismissed, pending review included. Does not use credits. get_list_results reads the projects on one list.

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

Input Schema

NameRequiredDescriptionDefault
limitNoLists per page. Free — config rows, not records.
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description only needs to add context — and it does: no credit consumption, the row shape (name, alreadyOnThis or projectCount, source), and the non-obvious fact that an alert and its companion list are the same match set minus dismissed items. That equivalence rule is information an agent could not derive from structured fields.

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 the resource definition, then row shape, then the alert-equivalence caveat, then the sibling pointer. Four short sentences, no filler; the alert/companion-list sentence is slightly digressive but carries real semantic value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the right thing by describing row fields, and it covers cost and sibling routing. It falls short on pagination semantics (offset behavior, total counts, default page size), which matters for a paged list tool with two parameters.

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

Parameters2/5

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

Only one of the two parameters (limit) is documented in the schema, and the description says nothing about either limit or offset — no page size guidance, no statement of what happens with pagination or how many rows come back by default. With 50% schema coverage the description should have compensated and does not.

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?

The description names the resource precisely — named lists on the account, including the Saved default (isDefault=true) and team-shared lists — and explicitly contrasts with get_list_results, which reads the projects inside one list. The verb 'list' is implied rather than stated, but the scope is unambiguous.

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?

It routes the agent to get_list_results for the contents of a single list, and notes no credits are consumed, which is useful selection context. However, it never states when to use this instead of sibling list-like tools (get_list, list_alerts, list_permit_alerts) or what prerequisites apply.

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