Skip to main content
Glama

mcp-notion__notion-view-version

Read-onlyIdempotent

Read a Notion page or database as it looked at a past time. The open page and other reads show only current content, so use this for any question about what a page said, contained, or looked like at an earlier date, even when the page is already open. A page returns its Markdown and properties; each inline database is a database tag, and you can pass that tag's url to this tool to read the database at the same time. A database returns its data sources, views, and rows. A linked database leaves out the data sources, views, and rows that belong to another database. Requires edit access to the page. 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": {
      "page": "<page>",
      "time": "<time>"
    },
    "name": "mcp-notion__notion-view-version"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page or database to read: a page URL, database URL, data source (collection://) URL, or ID.
timeYesThe moment to read, as an ISO 8601 time with a time zone offset. Convert the user's date and time in their own time zone, such as "2026-10-10T14:05:02-04:00" for 2:05 PM in New York. If the user names only a date, pick a time on that date in their time zone and tell them which.
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.
cursorNoA database's next_cursor, to read its next rows. Pass the same page and time as the call that returned it.
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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description nonetheless adds real behavioral detail beyond them: the return shape (Markdown plus properties; a database yields data sources, views, and rows), the linked-database gap, cursor pagination, and the edit-access prerequisite.

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?

Purpose is front-loaded, and each sentence covers a distinct fact (trigger, return shape, linked-database caveat, prerequisite, execution note). It is on the long side, and the closing note about the server marking it read-only overlaps with the annotations.

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?

For a six-parameter, two-required read tool with no output schema, the description covers what it returns, how results split between page and database forms, pagination, and the access prerequisite. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3 and the schema does most of the work. The description still adds meaning beyond it by explaining the tag/url relationship between an inline database and the `page` argument, tying the two reads to one call, which the schema does not spell out.

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?

'Read a Notion page or database as it looked at a past time' gives a specific verb, resource, and temporal modifier, and the next sentence explicitly contrasts it with current-content reads, so an agent can separate it from ordinary fetch/read tools without opening the schema.

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 a strong positive trigger: 'use this for any question about what a page said, contained, or looked like at an earlier date, even when the page is already open.' It also explains chained use (pass a database tag's url to read that database at the same moment). It stops short of naming a specific sibling alternative or stating when not to use it.

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