Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Move a folder

move_folder
DestructiveIdempotent

Move a Folder with every Folder, Thread and Note in it under parent_id (a Folder's id from list_folders), or to the top level (null: needs whole-workspace access); move_thread moves one Thread. Needs Can edit and organize; all of it and the destination must be within this connection's access, else unavailable. expected_revision is not compared. A Folder holding Threads needs the person's yes: your client may ask them, else it answers confirmation_required — ask, then send the same call with confirm. Answers a receipt with the new revision and url.

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>",
      "folder_id": "<folder_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "move_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoOnly after a confirmation_required answer and the person's yes: its details.confirm. Omit it otherwise.
folder_idYesA Folder's id, from list_folders or list_threads.
parent_idNoThe new parent Folder's id, or null for the top level.
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 only declare the mutation/idempotency/safety class; the description adds the substance: the move is recursive (all child Folders, Threads and Notes travel with it), permission prerequisites, access-scope failure modes, a two-step confirmation handshake triggered when the folder holds Threads, and a receipt containing the new revision and url. It also discloses the surprising fact that expected_revision is not compared, which an agent would otherwise wrongly assume guards the write.

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?

Front-loaded with the core action and densely packed with no filler sentences, but the phrasing is cramped — clauses like 'Needs Can edit and organize; all of it and the destination must be within this connection's access, else unavailable' and mid-sentence parentheticals force a re-read. Slightly tighter sentence breaks would improve scanability without losing content.

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, permission-gated, confirmation-gated mutation with no output schema, the definition covers everything an agent needs: preconditions, failure mode and recovery (confirmation_required then confirm), idempotent retry via operation_id, and the shape of the answer. Nothing material is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: parent_id=null means top level and demands whole-workspace access, expected_revision is explicitly not compared (contradicting the natural reading of the field), and confirm is tied to the confirmation_required answer rather than being an optional extra.

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 with scope: 'Move a Folder with every Folder, Thread and Note in it under parent_id ... or to the top level'. It also explicitly distinguishes itself from the sibling move_thread ('move_thread moves one Thread'), so an agent can pick the right tool without opening either schema.

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

Usage Guidelines4/5

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

Gives clear usage conditions: needs 'Can edit and organize' permission, folder and destination must be inside this connection's access, and null parent requires whole-workspace access. The confirmation branch is spelled out (send confirm only after confirmation_required plus the person's yes). It names the move_thread alternative but does not mention move_note as the single-note alternative, so a small routing gap remains.

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