Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_update_page_content

Destructive

Edits one Notion page's content as markdown, in one of three modes. edits replaces exact passages, each {old_str, new_str, replace_all_matches}; an edit whose old_str matches nothing is listed in warnings while the others apply. replace_with replaces the whole content. insert adds markdown at the start, at the end (the default), or after a selection. Child pages and databases are kept unless allow_deleting_content is true, and Notion refuses an edit that would remove them. The content of a synced page is not edited through Notion's API. Returns the page id and Notion's warnings.

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": "notion-mcp__notion_update_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoWith insert: a selection of existing content to insert after, written "start text...end text".
editsNoPassage replacements, at most 100, applied in one request. notion_get_page shows the markdown they match against.
insertNoMarkdown to add to the page, placed by position or after.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_idYesThe page's Notion id, with or without dashes, or a Notion URL that contains it (the id is read from the URL).
positionNoWith insert: start or end of the page. Default end.
allow_asyncNotrue lets Notion apply a large change in the background; the result is then a task id and carries no warnings.
replace_withNoMarkdown that replaces the page's whole content.
allow_deleting_contentNoWith edits or replace_with: true lets the change remove child pages and databases. Sent to Notion only when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses that child pages and databases are preserved unless allow_deleting_content is true, that Notion refuses edits removing them, that non-matching old_str values appear in warnings while other edits still apply, and that synced pages cannot be edited via the API. It also notes the return value (page id plus warnings).

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?

Front-loads the core action and mode enumeration, then layers edge-case behavior in short clauses. Every sentence carries distinct information (mode semantics, deletion safety, synced-page limit, return value) with no 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?

For a 9-parameter mutation tool with no output schema, the description covers mode selection, destructive side effects, partial-failure behavior, and the response shape. Nothing critical for a correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: which parameter belongs to which mode, that position defaults to end, and how old_str match failures surface as warnings. That relational context raises it above baseline.

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 ("Edits one Notion page's content as markdown") and immediately enumerates the three modes (edits, replace_with, insert). The focus on page *content* distinguishes it from the sibling notion_update_page, which handles page properties.

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?

Explains which mode to pick: edits for exact passage replacement, replace_with for whole-content replacement, insert for prepending/appending/inserting after a selection. It does not explicitly say when to prefer this over notion_update_page or notion_duplicate_page, but the mode guidance is clear and actionable.

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

All DataToRAG 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