Skip to main content
Glama

file_uploads

Upload files to Notion, supporting multi-part uploads for large files. Manage uploads with actions to create, send, complete, retrieve, and list.

Instructions

Upload files to Notion.

Actions (required params -> optional):

  • create (filename -> content_type, mode="single"|"multi_part", number_of_parts)

  • send (file_upload_id, file_content -> part_number): base64-encoded content

  • complete (file_upload_id)

  • retrieve (file_upload_id)

  • list (-> limit)

Max 20MB direct, multi-part for larger files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
file_upload_idNoFile upload ID (from create step)
filenameNoFilename (for create)
content_typeNoMIME type (for create, e.g. "image/png")
modeNoUpload mode (default: single)
number_of_partsNoNumber of parts (for multi_part mode)
part_numberNoPart number (for send in multi_part mode)
file_contentNoBase64-encoded file content (for send). Must be valid base64: only A-Z, a-z, 0-9, +, /, = chars. Use Buffer.from(bytes).toString("base64") to encode.
limitNoMax results for list
Behavior4/5

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

Annotations indicate non-read-only, non-destructive, non-idempotent behavior. The description adds value by detailing the multi-part upload process (create, send, complete) and file size limits. No contradictions with annotations.

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?

The description is concise (10 lines), well-structured with a clear action list and associated parameters, and front-loaded with purpose. Every sentence serves a purpose with no redundancy.

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?

Despite having no output schema, the description does not explain return values for actions like retrieve or list, nor does it cover error cases. For a multi-action tool, this is a significant gap that hinders an AI agent from anticipating results.

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?

Input schema has 100% coverage with descriptions for all 9 parameters. The description organizes parameters by action but does not add significant new semantic information beyond what the schema provides. Baseline score is appropriate.

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?

The description states 'Upload files to Notion' and enumerates specific actions (create, send, complete, retrieve, list), clearly identifying the resource and operation. It distinguishes from sibling tools like blocks or databases by focusing exclusively on file uploads.

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?

The description lists actions with required and optional parameters, and mentions size limits (20MB direct, multi-part for larger). However, it does not explicitly state when to use this tool versus alternatives, though siblings are clearly different in domain.

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/n24q02m/better-notion-mcp'

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