Skip to main content
Glama
Notion MCP Server

Notion MCP Server

notion_archive_page

Archives a Notion page using its page ID so outdated or unwanted pages can be removed from active workspace views.

Instructions

Archive a Notion page

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": {
      "pageId": "<pageId>"
    },
    "name": "notion_archive_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe ID of the page to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about reversibility (Notion archive moves to trash and is restorable), required permissions, or side effects on nested pages and blocks. 'Archive' alone is a large under-disclosure for a mutation tool.

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?

Four words, front-loaded with the action and resource, with zero filler. Its brevity is efficient structurally, though the missing detail is penalized under other dimensions.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description should explain what archiving does to the page and its children and whether the action is reversible. None of that is present, leaving the agent to guess at consequences.

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?

Only one parameter exists and the schema documents it fully (100% coverage) with 'The ID of the page to archive'. The description adds no extra meaning such as ID format or accepted URL forms, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Archive a Notion page'), which distinguishes it from sibling operations like notion_update_page or notion_get_page. It does not explicitly name those siblings or clarify how archive differs from update/delete, keeping it below a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to archive versus update or delete, no preconditions, and no note about whether archiving a parent affects child blocks. The agent must infer the usage policy entirely.

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