Skip to main content
Glama

mcp-notion__notion-download-skill

Read-onlyIdempotent

Download a spec-compliant Notion Skill as a complete tar.gz archive containing SKILL.md and its supporting files and nested folders. Pass the skill page ID. Returns a temporary signed url. Download and extract the archive to read or use the skill. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "id": "<id>"
    },
    "name": "mcp-notion__notion-download-skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifier for a Notion skill page.
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)
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds material context beyond that: the output is a tar.gz archive, the response is a temporary signed URL (ephemeral, must be fetched separately), and extraction is required before use. The closing note about the server marking it read-only and running straight away is useful but phrased in unclear internal jargon ('Through Royally').

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?

The core action and artifact are front-loaded in the first sentence, and each subsequent sentence covers a distinct step (input, return value, post-processing). Slightly marred by the oblique 'Through Royally: its server marks it read-only, so it runs straight away' clause, which costs a sentence without adding clear meaning.

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?

With no output schema, the description does the work of explaining what comes back — a temporary signed URL pointing at a tar.gz archive of SKILL.md plus nested support files. Combined with full annotation coverage, an agent has enough to call and consume the result, though the lifecycle of the temporary URL (expiry, renewability) is left unstated.

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?

Schema description coverage is 100%, so the schema already documents all four parameters including the id, the tracking-only 'skill' field, the fixed site_id enum, and instructions_version. The description only restates the required id parameter ('Pass the skill page ID') and adds no format or syntax detail for the remaining fields. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific verb and resource ('Download a spec-compliant Notion Skill') and specifies the delivered artifact ('complete tar.gz archive containing SKILL.md and its supporting files and nested folders'). This clearly separates it from the sibling notion-download-attachment, which deals with attachments rather than packaged skills.

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

Usage Guidelines3/5

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

It tells the agent how to invoke ('Pass the skill page ID') and what to do afterwards ('Download and extract the archive to read or use the skill'), which implies the use case. However, it never states when this tool should be chosen over alternatives such as notion-fetch for reading a skill page, nor any preconditions or exclusions.

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