Skip to main content
Glama

List lists

list_lists
Read-only

Use this when the user wants to see their lists or asks which lists exist, or to find a list's id from its name. Shows the organization's lists, newest first, each with its kind, folder and row count: all of them, one kind with type, one folder's with folderId, or those whose name contains search. For the next page, send the page's next cursor with the same filters. Free.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly lists of this kind.
cursorNoThe `pagination.nextCursor` of the page before. Later pages keep the first page's size.
searchNoOnly lists whose name contains this text, in any case.
folderIdNoOnly the lists in this folder.
pageSizeNoLists per page.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, so credit goes to the added context: newest-first ordering, the returned fields (kind, folder, row count), page-continuation behavior, and that calls are free. 'Free' is slightly unexplained (no credit cost vs. no rate limit), keeping it from a 5.

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?

Dense and front-loaded: trigger condition first, then filter modes, then pagination, then cost. Every clause carries information, though the trailing 'Free.' fragment and the tightly packed filter listing make it marginally less scannable than it could be.

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 five-parameter, no-output-schema read tool, the description supplies what an agent needs to call it correctly: trigger conditions, filter combination rules, pagination continuation, ordering, and the shape of returned rows. Nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining that the filters are mutually selectable modes and that the cursor must be resent 'with the same filters', which the schema does not state. It also clarifies search is a substring match, duplicating the schema description slightly but reinforcing semantics.

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 plus the concrete user intents it serves ('see their lists', 'which lists exist', 'find a list's id from its name'), which separates it cleanly from get_list, list_folders and the list_* siblings. An agent can route on the description alone.

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 explicit triggering conditions and lays out the four filter modes (all, by type, by folderId, by name substring), which tells the agent exactly when each parameter applies. It stops short of naming alternative tools (e.g. get_list for a single list's details), so no explicit when-not guidance.

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