notion-full-mcp

by cphoskins

Overview Schema Source Related Servers Discussions Admin

Python

Remote

upload_file

Upload a local file to Notion storage and return a file_upload_id for referencing in image, file, PDF, or video blocks.

Instructions

Upload a file to Notion's own storage.

Returns a file_upload_id that can be referenced in image, file, pdf, or video blocks via {"type": "file_upload", "file_upload": {"id": ...}}. For the common case of uploading an image and creating a block in one step, use upload_image_as_block instead.

Args: file_path: Local path to the file (PNG, JPEG, GIF, SVG, PDF, etc.), up to 20 MiB.

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": "upload_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	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

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write/open-world profile is covered. The description adds real value with the returned file_upload_id, the exact reference shape for image/file/pdf/video blocks, and the 20 MiB size ceiling and accepted formats. It says nothing about failure behavior, auth requirements, or whether identifiers expire.

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?

Purpose is front-loaded, the return value and its usage shape follow, the alternative tool is named next, and the arg constraints close it out. Every sentence carries information and none is redundant.

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?

For a one-parameter upload with an output schema already present, the description covers the return value semantics, format support, size limit, and the main sibling alternative. The remaining gap is operational context such as auth or overwrite behavior, which is minor for this tool.

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 0% and the single parameter is a bare string, so the description must carry the meaning. It does: file_path is a local path, with example formats (PNG, JPEG, GIF, SVG, PDF) and a hard 20 MiB limit that the schema does not express anywhere.

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 ("Upload a file to Notion's own storage") and immediately contrasts it with the sibling upload_image_as_block for the combined upload-and-create-block case, so an agent can tell them apart without opening a schema.

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?

Gives clear context for when this tool is the right choice and explicitly routes the common image-plus-block case to upload_image_as_block. It stops short of naming upload_file_as_block or spelling out exclusions beyond that one case, but the primary selection condition is stated.

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