notion-full-mcp

Overview Schema Source Related Servers Discussions Admin

restore_page

Idempotent

Restore a trashed Notion page and its child pages, including descendants removed by a cascading delete. Use this as the supported way to unarchive a page.

Instructions

Restore a page (and its children) from trash.

This is the explicit counterpart to delete_block on a page. update_page has a safety guard that blocks archived=False; this dedicated tool is the supported way to unarchive.

When called on a page that was archived via a cascade (for example, a section container that was deleted along with its subpages), restoring the parent container automatically restores the cascaded descendants.

Args: page_id: The page to restore from trash.

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_id": "<page_id>"
    },
    "name": "restore_page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety profile (readOnly=false, destructive=false, idempotent=true), and the description adds genuinely non-obvious behavior: cascade restoration of descendants when the parent was archived as part of a section container. It does not mention permission requirements or what happens if the page is not in trash, keeping 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence followed by two tight paragraphs on alternatives and cascade semantics. There are minor formatting artifacts (backticks and a reST-style Args block) but no filler prose.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations convey safety. However, for a mutation tool the description omits error/edge behavior (page not in trash, already active) and permission prerequisites, leaving a moderate 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 description coverage is 0%, so the description must carry parameter meaning. It only says 'The page to restore from trash', which clarifies context but gives no ID format, source (URL vs. UUID), or constraints on page_id.

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 ('Restore a page (and its children) from trash') and explicitly contrasts itself with delete_block and update_page, so an agent can distinguish it from siblings without opening 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 states when to use this tool (unarchiving a page), when the obvious alternative fails (update_page has a safety guard blocking archived=False), and what the sibling delete_block's inverse is. That is explicit routing plus an exclusion.

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