Skip to main content
Glama

mcp-notion__notion-download-attachment

Read-onlyIdempotent

Download the contents of a small UTF-8 text attachment created by the Notion MCP create-attachment tool.

Pass the file_upload_id returned by create-attachment. The attachment must belong to the requesting integration, have completed uploading, and use a supported text format such as HTML, Markdown, plain text, CSV, JSON, XML, CSS, YAML, TSV, calendar, GPX, or SVG.

The response contains the complete text in content so you can save it locally, edit it, and call create-attachment again to upload a new version. Downloads are limited to 200 KiB. This tool does not fetch arbitrary URLs or return binary files. For larger or binary attachments, use the signed file URL returned when reading the containing Notion page.

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_upload_id": "<file_upload_id>"
    },
    "name": "mcp-notion__notion-download-attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
file_upload_idYesThe FileUpload ID returned by the create-attachment tool.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior on top: a hard 200 KiB size cap, the text-only format allowlist, the requirement that the upload finished and is owned by the same integration, and the presence of a `content` field in the response. That is exactly the kind of constraint an agent needs before calling.

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?

Front-loaded with the core action, then prerequisites, then limits and alternatives, plus a compact example. It is slightly padded by the example block and a stray trailing sentence ("Through Royally: its server marks it read-only...") that reads as noise rather than tool documentation.

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?

No output schema exists, and the description compensates by naming the `content` field and its semantics. Combined with size limits, format constraints, and fallback guidance, the definition is nearly self-sufficient; only the error behavior for unsupported formats or oversized files is left unstated.

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 100%, so the schema already documents all four parameters. The description nonetheless adds provenance meaning for the only required parameter — that `file_upload_id` must be the value returned by create-attachment and must reference a completed upload — which is value beyond the terse schema text.

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 ("Download the contents of a small UTF-8 text attachment") and ties it to the producing tool (create-attachment), so an agent can distinguish it from notion-fetch or page-reading siblings without inspecting schemas.

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

Usage Guidelines5/5

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

Gives explicit preconditions (must belong to the requesting integration, upload must be complete, must be a supported text format), an explicit exclusion ("does not fetch arbitrary URLs or return binary files"), and names the alternative path for those cases (the signed file URL returned when reading the containing page). It also describes the round-trip workflow of re-uploading an edited version.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources