Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Move a thread

move_thread
DestructiveIdempotent

Move a Thread into a Folder or to the top level; it keeps its id, Notes and history. move_note moves one Note, move_folder a whole Folder. folder_id: a live Folder from list_folders. Needs Can edit and organize. expected_revision is not compared: the last move wins. Answers a receipt with the new revision and url; the same operation_id answers it again instead of moving twice.

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": "move_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idNoThe Folder's id, or null for the top level (whole-workspace access).
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.6/5.0
Behavior4/5

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

Beyond the annotations it discloses preservation semantics (id, Notes and history survive), the concurrency policy ("expected_revision is not compared: the last move wins"), and idempotency behavior ("the same operation_id answers it again instead of moving twice"). The return shape is summarized as a receipt with the new revision and url. minor gap: it does not say whether this requires any auth scope beyond the stated permission, and it doesn't mention what happens to the thread's old folder position.

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?

It is short and front-loads the core action, followed by the sibling routing and then semantics. The line-wrapped run-on phrasing ("...history.\nmove_note moves...") is slightly awkward but nothing is redundant.

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 carries the return value (a receipt with new revision and url) and the retry contract. Combined with full schema coverage and annotations, an agent has everything needed to call this destructive move correctly.

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 still adds useful meaning by explaining that folder_id must be a live Folder and that expected_revision is ignored, with the resulting last-writer-wins semantics. It does not add anything about operation_id beyond what the schema already says.

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 opens with a specific verb and resource plus the destination set: "Move a Thread into a Folder or to the top level." It then explicitly separates itself from move_note and move_folder, so an agent can pick the right tool without inspecting schemas.

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 both alternatives (move_note for a single Note, move_folder for a whole Folder) and states the prerequisite that folder_id must come from list_folders and that the caller needs 'Can edit and organize'. The null/top-level case is also routed in the first clause.

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