Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Move a thread to Trash

trash_thread
DestructiveIdempotent

Move a Thread and its Notes to Trash; restore_thread brings them back. To keep a finished Thread readable, use archive_thread instead. Refused while a Note in it has an open request (request_open). Needs Can edit and organize; expected_revision is not compared. Answers a receipt whose url opens Trash.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation_id": "<operation_id>",
      "thread_id": "<thread_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "trash_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesA Thread's id, from list_threads, search or a read.
operation_idYesA new UUID for each write. After a lost answer, send the identical call with the same one, or check get_operation before writing again.
expected_revisionYesIts revision from list_threads, get_thread, list_folders or get_note (not a content_revision); not compared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / expected_revision / description
      Previous value: -"The revision you last read for it."New value: +"Its revision from list_threads, get_thread, list_folders or get_note (not a content_revision); not compared."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds what they cannot: the refusal condition, the required permission ('Can edit and organize'), and the fact that expected_revision is not compared. It also describes the return shape ('a receipt whose url opens Trash'), valuable because there is no output schema.

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?

Four compact clauses, each carrying distinct information: scope, inverse operation, alternative for a different intent, precondition, permission, and return. The alternative and the refusal are front-loaded where an agent will read them first, with no filler.

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 destructive, three-required-parameter tool with no output schema, the description covers permissions, refusal semantics, recovery path, and the receipt return value. Nothing an agent needs to call it safely and correctly is missing.

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 all three parameters are already documented, including that expected_revision comes from list_threads/get_thread and is not a content_revision. The description adds only the 'not compared' nuance, which the schema also states, so it does not meaningfully extend parameter meaning beyond baseline.

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 ('Move a Thread and its Notes to Trash') and immediately scopes the blast radius to the thread plus its notes. It names the sibling that undoes it (restore_thread) and the sibling it is not (archive_thread), so an agent can distinguish it without opening another 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?

Gives explicit when-to-use-this vs alternative guidance: archive_thread for a finished thread that should stay readable, restore_thread to reverse. It also states the blocking condition ('Refused while a Note in it has an open request (request_open)'), which is exactly the kind of precondition that prevents a failed call.

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