Skip to main content
Glama

Restore a page from Trash

restore_page

Bring a page back from Trash (the inverse of delete_page) — its private link starts working again. Identify the page with page (its viewer URL or slug). Only works while the page is still in your Trash; a page that has already been permanently purged can't be restored. You can only restore your own pages.

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": {
      "page": "<page>"
    },
    "name": "restore_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe viewer URL or slug of a page currently in your Trash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the observable effect (the private link starts working again), a hard state precondition (still in Trash, not purged), and an authorization boundary (own pages only). It does not say what an error or partial-failure response looks like, which keeps it short of a 5.

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?

Three tight sentences: effect first, then the parameter, then the constraints. The parenthetical naming delete_page is high-value context packed into two words, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation with no annotations and no output schema, the description covers effect, precondition, and permission scope, which is what an agent needs to call it correctly. Return-value detail isn't required here since there is no output schema, leaving only error semantics as a minor gap.

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 coverage is 100% and the schema already defines `page` as "the viewer URL or slug of a page currently in your Trash." The description's "Identify the page with `page` (its viewer URL or slug)" restates that rather than adding format examples or fallback behavior, so the baseline 3 applies.

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 ("Bring a page back from Trash") and explicitly positions itself as "the inverse of delete_page," so an agent can distinguish it from delete_page and the other siblings without opening any 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?

It states clear preconditions and exclusions: the page must still be in Trash, purged pages cannot be restored, and only the caller's own pages qualify. What's missing is routing to an alternative when those conditions fail (e.g., a search/list tool to find the page first), but the when/when-not guidance is explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources