Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

List threads

list_threads
Read-onlyIdempotent

List Threads a page at a time, optionally only those directly in folder_id (from list_folders). Each has id, title, description, status (a key from list_statuses) and status_name, folder, revision, archived, trashed and last_activity_at, which can lag a minute behind someone typing. A Thread is one ongoing subject; its Notes hold the work: read them with get_thread. To find a Thread by what it is about, use search.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value on top: page-at-a-time semantics, the full field set returned (important since there is no output schema), and a staleness caveat that last_activity_at 'can lag a minute behind someone typing'. It does not state default ordering or what next_cursor looks like, keeping it short of 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?

Purpose and scope are front-loaded in the first clause, followed by return-shape and alternative-routing sentences. The mid-sentence field enumeration is dense and reads slightly run-on, but every sentence carries information the agent needs.

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?

With no output schema, the description correctly takes on the burden of describing returned fields, and it covers pagination, filtering, and staleness behavior. Combined with the annotations, nothing an agent needs to call this correctly 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 slightly beyond it by giving provenance for folder_id ('from list_folders') and tying the status field to list_statuses, which helps an agent know where valid values come from; it adds no detail on limit bounds or cursor mechanics beyond the schema.

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?

Opens with a specific verb+resource+scope: 'List Threads a page at a time, optionally only those directly in folder_id'. It also enumerates the returned fields and explicitly contrasts itself with get_thread and search, so an agent can separate it from siblings without opening any 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?

It names two concrete alternatives with the condition that selects each: 'its Notes hold the work: read them with get_thread' and 'To find a Thread by what it is about, use search.' That is explicit routing guidance rather than implied usage.

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