Skip to main content
Glama

mcp-notion__notion-fetch

Read-onlyIdempotent

Retrieves details about a Notion entity (page, database, data source, or saved database view) by URL or ID.

Provide a URL or ID in id. Make multiple calls for multiple entities.

For pages, use path, verification, edit time, and truncation metadata to assess the source. Treat recency as context, not proof. Report material uncertainty when sources conflict.

Pages use Notion-flavored Markdown. For the complete specification, read the MCP resource notion://docs/notion-flavored-markdown-spec through your MCP client's resource-reading interface, or call the Notion "fetch" tool with this URI if your client does not support reading MCP resources. Do NOT pass this URI to any other URL-fetching tool.

Pass a notion://docs/* URI as id to read that MCP documentation resource.

Databases return data sources in <data-source url="collection://..."> tags. Fetch the collection:// URL for its schema and use it with update_data_source or query_data_sources. Multi-source databases return more than one data source. … 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-fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID or URL of the Notion page, database, or data source to fetch. Supports notion.so URLs, Notion Sites URLs (*.notion.site), raw UUIDs, and data source URLs (collection://...). Pass "memory" to fetch the connected user's About page and memory database in this workspace without creating them. Pass a notion://docs/* URI to read that documentation resource. Also accepts an explicit saved view URL (view://...) from a database response. If a database block ID returns a validation error, use the collection:// URL from that error. Example: <example>notion://docs/notion-flavored-markdown-spec</example>.
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)
include_file_urlsNoWhether to return signed download URLs for uploaded files. Defaults to false. When false, page Markdown cites uploaded files by stable notion-file-block:// references and the response has no references map; call get_file_download_urls with the references when you need those files' contents. When true, the response's references map gives the signed URL for each reference.
include_transcriptNoWhether to include meeting note transcripts. Defaults to false. When true, full transcripts are included; when false, a placeholder with the meeting note URL is shown instead.
include_discussionsNoWhether to include discussion/comment indicators in the page output. When true, adds a <page-discussions> summary with discussion count, preview snippets, and discussion:// URLs. Use with the get_comments tool to retrieve full discussion content. Defaults to false.
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.8/5.0
Behavior3/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 that pages come back as Notion-flavored Markdown with path, verification, edit-time and truncation metadata, and that multi-source databases return multiple <data-source> tags — useful behavior beyond the annotations. The trailing fragment about the server marking it read-only is garbled and adds little.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and mostly well organized into short paragraphs by concern. However it is long, and the final sentence ('… Through Royally: its server marks it read-only, so it runs straight away') is a truncated, confusing fragment that costs the reader more than it gives.

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 7 parameters, no output schema, and read-only annotations, the description covers addressing formats, markdown conventions, data-source expansion, and flag behaviors (transcripts, discussions, file URLs). It does not explain response shape or pagination/size limits for large pages, which is the main remaining gap.

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 baseline is 3. The description does add workflow meaning not in the schema — that a collection:// URL returned from a database should be fed back in as id, and that notion://docs/* URIs are valid id values — but the per-parameter formats (memory, view://, notion.site URLs) are already spelled out in the schema itself.

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 and enumerates the entity types covered (page, database, data source, saved database view) as well as the two addressing modes (URL or ID). An agent can immediately tell this is the read/retrieve primitive, distinct from search or list siblings.

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 real operational guidance: 'Make multiple calls for multiple entities', fetch the collection:// URL returned by a database to get its schema, use it with update_data_source or query_data_sources, and pass notion://docs/* URIs as id to read docs. It does not explicitly say when to prefer a search/list sibling (e.g. notion-search) over this tool, so 4 rather than 5.

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