Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Archive a thread

archive_thread
DestructiveIdempotent

Archive a finished Thread: it leaves the active list, stays readable (list_threads with state "archived") and becomes read-only until unarchive_thread brings it back. To discard a Thread, use trash_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 Archive.

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": "archive_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?

The description adds substantial behavior beyond annotations: the archived Thread stays readable, becomes read-only, is reversible via unarchive_thread, can be refused due to an open request, needs permissions, and returns a receipt with an Archive URL. These details are not merely restatements of readOnlyHint, idempotentHint, or destructiveHint.

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?

The description is compact and front-loaded: it states the action and state transition first, then alternatives, refusal conditions, permissions, and return behavior. Every sentence contributes useful operational context without 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 mutating, reversible archive operation with no output schema, the description covers the key states, sibling alternative, refusal condition, permission requirement, revision behavior, and return receipt. An agent has enough information to invoke it correctly and avoid confusing it with trash_thread.

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 already 100%, so the schema documents thread_id, operation_id, and expected_revision thoroughly. The description only reinforces that expected_revision is not compared, which is already present in the schema, and adds no new syntax or format guidance for parameters.

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?

The description states a specific verb and resource: archiving a finished Thread. It clearly describes the resulting state (leaves active list, remains readable via list_threads with state archived, becomes read-only until unarchive_thread) and distinguishes it from trash_thread.

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 explicitly says to use trash_thread instead when discarding a Thread, which is a clear alternative. It also gives when-not conditions: refused while a Note in it has an open request, and requires Can edit and organize.

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