Skip to main content
Glama

create_page_from_file

Create a Notion page by specifying a local markdown file path; the server reads and validates the file directly, avoiding content transmission through the agent context.

Instructions

Create a Notion page from a local markdown file. The server reads and validates the file, then creates the same result as create_page without sending file contents through the agent context.

STDIO MODE ONLY. This tool is not available when the server runs over HTTP, because in HTTP mode the server's filesystem belongs to the server host, not the caller.

Restrictions:

  • file_path must be an ABSOLUTE path (no relative paths, no ~ expansion)

  • File must be inside the configured workspace root (defaults to the server's process.cwd(); override via the NOTION_MCP_WORKSPACE_ROOT env var)

  • File extension must be .md or .markdown

  • File size must be ≤ 1 MB (1,048,576 bytes)

  • File must be valid UTF-8

  • Symlinks are resolved and the resolved path must still be inside the workspace root

For supported markdown syntax, read resource easy-notion://docs/markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPage title
file_pathYesAbsolute path to a local .md or .markdown file (≤ 1 MB, UTF-8, inside the configured workspace root)
parent_page_idNoParent page ID. Same resolution rules as create_page.
Behavior4/5

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

Describes that the server reads/validates the file and creates the same result as 'create_page'. Details numerous restrictions (absolute path, workspace root, file type, size, UTF-8, symlinks). No annotations provided, so description carries burden; it does not mention auth or return value but is thorough overall.

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?

Well-structured with clear paragraphs: purpose/behavior, mode restriction, bulleted restrictions, and resource reference. Every sentence is informative with no redundancy.

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?

Covers purpose, mode, restrictions, references related tool and resource. No output schema, but refers to 'create_page' result. Lacks error handling details but sufficient given complexity.

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 provides descriptions for all 3 parameters (100% coverage). Description adds semantic value by clarifying workspace root, file size limit, UTF-8 validation, and symlink resolution beyond the schema's descriptions.

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?

Clearly states 'Create a Notion page from a local markdown file', specifying verb, resource, and input source. Distinguishes from sibling 'create_page' by noting it avoids sending file contents through agent context and is STDIO mode only.

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?

Explicitly states when to use (local markdown file to avoid content transfer) and mode restriction (STDIO only). Compares to 'create_page' and references a resource for markdown syntax. Lacks explicit when-not-to-use scenarios beyond mode.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grey-Iris/easy-notion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server