notion-private-api-mcp

Sync Markdown File

sync_markdown_file

Sync a local Markdown file to Notion by creating a new page or replacing an existing page's content. Specify file path and optional page ID for replacement.

Instructions

Create a new page or replace an existing page from a local Markdown file.

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": {
      "file_path": "<file_path>"
    },
    "name": "sync_markdown_file"
  }
}

Input Schema

Name	Required	Description
`file_path`	Yes	Absolute or relative Markdown file path.
`page_id`	No	Existing page id to replace.
`parent_page_id`	No	Parent page id when creating a new page.
`title`	No	Optional page title override.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 31, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, and description only states 'create or replace' without detailing conditions (e.g., which parameter triggers creation vs replacement), overwrite behavior, idempotency, or required permissions. Minimal disclosure.

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?

Single concise sentence, front-loaded with key action. Could be improved with structuring (e.g., bullet points), but no wasted words.

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?

Description lacks behavioral details for a 4-parameter tool with no output schema or annotations. Missing info on parameter interactions, return values, and error scenarios, leaving gaps for agent decision-making.

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%, so description adds little beyond schema. It provides context ('local Markdown file') but does not enhance individual parameter meaning.

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?

Description clearly states 'create a new page or replace an existing page from a local Markdown file', specifying verb and resource. It implies a file-based operation, distinguishing it from other page tools like create_page or replace_page_content, but lacks explicit contrast.

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

Usage Guidelines3/5

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

Description suggests usage when syncing a local Markdown file to a page, but provides no guidance on when to choose this tool over alternatives (e.g., create_page, replace_page_content) or when not to use it.

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

Deploy Server