Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_get_page

Read-only

Reads one Notion page: its title, url, parent, timestamps and properties, and its content as markdown. Properties come back as plain values keyed by property name, for example {"Status": "Done", "Assignee": ["Test User"], "Due": "2026-10-20"}. A database row is a page, so a row's id returns that row. The markdown is Notion's own rendering; truncated is true when Notion cut it short (very long pages), and unknown_block_ids lists blocks with no markdown form, such as embeds and link previews. A page that is not shared with the DataToRAG connection reads as not found.

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": {
      "page_id": "<page_id>"
    },
    "name": "notion-mcp__notion_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_idYesThe page's Notion id, with or without dashes, or a Notion URL that contains it (the id is read from the URL).
include_markdownNoWhether to fetch the page content as markdown, which is a second request. Default true. False returns the properties alone, which is enough to read a database row's values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses that markdown is Notion's own rendering, that truncated indicates Notion shortened very long pages, that unknown_block_ids lists blocks with no markdown form (embeds, link previews), and that unshared pages surface as not found. These are failure modes and output quirks an agent cannot infer from annotations or schema.

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?

Five sentences, front-loaded with the return payload, then edge cases. Dense and mostly waste-free, though the inline property example is verbose relative to the value it adds.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden and does so: it describes the returned object's fields, the shape of properties, and the two markdown edge cases. An agent can call this correctly and interpret the result without further documentation.

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 already 100%, so the baseline is 3, but the description adds real meaning: page_id may be a bare id or a URL containing it, and include_markdown=false is explicitly sufficient for reading database-row values. It also shows the concrete shape of returned properties with a worked example.

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 opens with a specific verb+resource ("Reads one Notion page") and enumerates exactly what comes back: title, url, parent, timestamps, properties, and markdown content. It also resolves the ambiguity with page-like siblings by stating that a database row is a page, so row ids resolve here.

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?

It gives clear situational context — use this for a row's values, and set include_markdown false when only properties are needed — but never names an alternative tool (e.g. notion_get_database or notion_search) or states when not to use it. Guidance is actionable yet not exhaustive.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources