Skip to main content
Glama

List collections

list_collections
Read-onlyIdempotent

Lists collections, optionally filtering by title. Use get_collection to inspect content. Pass next_cursor with the same query to continue.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
cursorNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful pagination behavior (continuation with the same query), but it calls the parameter "next_cursor" while the schema names it "cursor", which risks an agent passing the wrong key or guessing a field name.

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 purpose, then the alternative, then the pagination rule. No filler and nothing buried.

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 simple read-only list tool with rich annotations and no output schema, the description covers purpose, the sibling alternative, and pagination. The main gaps are page_size and the cursor naming mismatch, both of which are small but could cause a fumbled call.

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 0%, so the description must carry parameter meaning. It does explain that query filters by title and that the cursor continues the same query, but page_size is never mentioned and the cursor is referred to by a name that does not match the schema property, leaving the agent to reconcile the two.

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?

"Lists collections, optionally filtering by title" gives a specific verb plus resource and the filter scope, and it explicitly separates this tool from get_collection (which inspects content). It stops short of 5 only because the core phrasing largely mirrors the name/title, with the differentiation carried by the second sentence.

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?

It routes the agent to get_collection when content inspection is needed, and tells the agent how to continue a listing via cursor. There is no explicit when-not guidance (e.g. browsing the whole library vs. searching by title), but the alternative is named with a clear condition.

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