Skip to main content
Glama
katekruger

notion-plus-mcp-server

by katekruger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Change History

notion_history
Read-onlyIdempotent

List recent changes made through this Notion MCP server, newest first, with undo IDs, how much each undo can revert, and inputs for interrupted or failed entries to inspect and recover edits.

Instructions

List changes made through this server, newest first, with their undo ids and how much of each undo can revert. Entries marked interrupted or failed stopped part-way; their input is included so the objects can be checked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNonext_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "next_cursor from the previous page.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.10.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for going further: it discloses result ordering, that entries carry undo ids with revert scope, and that interrupted/failed entries stopped part-way with input retained. This partial-failure semantics is genuinely useful and not derivable from annotations.

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?

Two dense sentences, front-loaded with the tool's purpose and no filler. The second sentence about interrupted/failed entries is slightly cryptic but earns its place by clarifying an edge case in the results.

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 usefully characterizes the return payload (undo ids, revert extent, partial-failure entries), which is exactly what an agent needs. The remaining gap is pagination — the cursor param exists but nothing explains paging behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about limit or cursor, and schema coverage is only 50% (limit is undocumented in the schema). With half the parameters lacking any definition, the description needed to compensate for limit's default and max, but it adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb (list) and resource (changes made through this server), plus ordering (newest first), so the agent immediately knows this is a change-log reader. It distinguishes itself from notion_undo only implicitly by surfacing undo ids rather than naming the sibling, so it falls short of a 5.

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?

Usage is implied rather than stated: surfacing undo ids and revert scope suggests reviewing history before calling notion_undo, but the description never says when to use this versus notion_undo, nor names any exclusion. Adequate context, no explicit guidance.

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

Deploy Server

Other Tools