Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Restore a folder

restore_folder
Idempotent

Bring a Folder back from Trash (list_folders with state "trash" finds it) into its parent, with the Folders, Threads and Notes that went to Trash with it; ones trashed on their own stay there (restore_thread, restore_note). If its parent is in Trash too, restore that first (target_deleted). Needs Can edit and organize; expected_revision is not compared. 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": "restore_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesA Folder's id, from list_folders or list_threads.
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 indicate non-readonly, idempotent, and non-destructive behavior, but the description adds substantial context beyond them. It discloses cascade scope (Folders, Threads and Notes trashed with it), permission requirements ('Can edit and organize'), the parent-in-trash failure condition target_deleted, that expected_revision is not compared, and the receipt containing new revision and url.

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 four dense but purposeful sentences, front-loading the action and scope before prerequisites, permissions, and return behavior. Parentheticals are efficient and no sentence is 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?

Given a restore mutation with no output schema but a fully documented input schema and annotations, the description covers cascade effects, permissions, parent-restore precondition, and return receipt. Nothing an agent needs in order to call it 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 the baseline is 3. The description restates that expected_revision is not compared and adds that the folder can be found via list_folders with state 'trash', but it does not add meaningful operation_id semantics 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?

Uses the specific verb 'Bring a Folder back from Trash' and clearly identifies the resource as a Folder. It explicitly distinguishes this from restore_thread and restore_note for items trashed on their own, so an agent can tell it is a folder-level cascade restore.

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?

States the trigger condition (folder is in Trash and findable via list_folders with state 'trash'), the prerequisite (restore parent first if the parent is also in Trash), and the alternatives for individually trashed items. This gives explicit when-to-use and when-not-to-use guidance.

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