Skip to main content
Glama

Notion_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Notion Get Page

notion_get_page
Read-onlyIdempotent

Get a Notion page by ID. Returns full properties, metadata, and content structure for reading or editing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesNotion page ID (UUID format, with or without dashes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPage ID
urlNoNotion web URL for the page
objectNoObject type ('page')
parentNoParent object reference
archivedNoWhether page is archived
created_byNoCreator user object
propertiesNoPage properties and field values
created_timeNoISO 8601 creation timestamp
last_edited_byNoLast editor user object
last_edited_timeNoISO 8601 last edit timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "description": "Whether page is archived",
+      "type": "boolean"
+    },
+    "created_by": {
+      "description": "Creator user object",
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "object": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "created_time": {
+      "description": "ISO 8601 creation timestamp",
+      "type": "string"
+    },
+    "id": {
+      "description": "Page ID",
+      "type": "string"
+    },
+    "last_edited_by": {
+      "description": "Last editor user object",
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "object": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "last_edited_time": {
+      "description": "ISO 8601 last edit timestamp",
+      "type": "string"
+    },
+    "object": {
+      "description": "Object type ('page')",
+      "type": "string"
+    },
+    "parent": {
+      "description": "Parent object reference",
+      "properties": {
+        "database_id": {
+          "type": "string"
+        },
+        "page_id": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "properties": {
+      "description": "Page properties and field values",
+      "type": "object"
+    },
+    "url": {
+      "description": "Notion web URL for the page",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "page_id": "550e8400e29b41d4a716446655440000"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that the tool returns 'full properties, metadata, and content structure for reading or editing', which contextualizes the return value. No contradiction with annotations.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no redundant words. Every part serves a purpose, making it efficient for an AI agent to parse.

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?

Given the simplicity of the tool, the description adequately covers its purpose and return content. The presence of an output schema reduces the need to detail return values. Minor gap: could clarify if it works with archived pages, but not critical.

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?

The single parameter 'page_id' is fully documented in the input schema (100% coverage). The description does not add any extra meaning or usage hints beyond what the schema provides, meeting the baseline.

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 uses a specific verb ('Get'), identifies the resource ('Notion page'), and clarifies the scope ('by ID'). It contrasts with sibling tools like 'notion_get_database' and 'notion_list_pages', making its distinct role clear.

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?

The description implies usage for fetching a single page but provides no explicit guidance on when to use or avoid this tool vs alternatives. No when-not or prerequisite information is given.

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

All Notion_connect 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