Skip to main content
Glama

file_uploads

Upload files to Notion with support for single and multi-part uploads. Manage upload sessions by creating, sending parts, completing, retrieving, and listing file uploads.

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
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description reveals the multi-step upload flow, file size limits, base64 encoding requirements, and multi-part part numbering. This fully informs the agent of behavioral traits and constraints.

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 and well-structured: a brief purpose statement followed by a clear list of actions with their parameter requirements. Every sentence adds value, and the information hierarchy is immediately apparent.

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?

Given 9 parameters, a multi-step workflow, and no output schema, the description adequately covers the upload process (create→send→complete) and the list action. However, it omits details on what retrieve returns and does not specify if any results are paginated, leaving minor gaps.

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

Parameters5/5

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

The input schema already includes descriptions for all 9 parameters (100% coverage), but the description adds critical grouping by action, indicates required vs optional per action, and provides base64 encoding format guidance. This significantly enhances parameter understanding beyond the schema alone.

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 clearly states 'Upload files to Notion' and enumerates five actions (create, send, complete, retrieve, list) with distinct purposes. This specific verb-resource pairing and action breakdown effectively distinguishes it from sibling tools like blocks or pages.

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 provides action-specific required/optional parameters and explains when to use multi-part vs single upload via the size limit (20MB threshold). However, it does not explicitly exclude scenarios or compare directly with alternatives, slightly reducing guidance completeness.

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