Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

List folders

list_folders
Read-onlyIdempotent

List the Folders this connection can see, a page at a time. Each has id, name, parent_id, revision, trashed and shared; parent_id builds the tree (null at the top level, or when the parent is outside access). Folders are optional and many Threads sit at the top level: to find a Thread, use list_threads or search. A Folder's id goes to list_threads, create_thread, move_thread and create_folder.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1–50.
stateNo"active" (default), "trash" or "all".active
cursorNonext_cursor from the previous page; omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds context the annotations cannot: paged results ("a page at a time"), the exact fields returned per folder, and the null conventions for parent_id at top level or when the parent is out of scope. It does not state the page size ceiling or ordering, which would complete the picture.

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 sentences, front-loaded with purpose, then return shape, then routing guidance. Every clause carries information an agent needs, and the sibling redirection is placed last where it is easy to act on.

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?

There is no output schema, so the description compensates by enumerating the returned fields (id, name, parent_id, revision, trashed, shared) and explaining the tree-building semantics of parent_id. Pagination, access scoping, and the handoff to other tools are all covered for a simple three-parameter read 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%, so limit, state and cursor are fully documented structurally and the baseline is 3. The description only weakly reinforces them ("a page at a time" gestures at cursor) and adds no format or edge-case detail beyond the schema, though it does explain the meaning of the parent_id field callers will use.

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 ("List the Folders this connection can see") with the scope qualifier that it is access-limited, and immediately distinguishes the resource from Threads. An agent can tell this apart from list_threads or search without opening a schema.

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

Usage Guidelines5/5

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

Explicitly says Folders are optional, that many Threads sit at the top level, and names the alternatives to use instead ("to find a Thread, use list_threads or search"). It also names the downstream consumers of a Folder id (list_threads, create_thread, move_thread, create_folder), which tells the agent why to call this first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ThreadPage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources