Skip to main content
Glama
Sign In

Notion_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Notion List Pages

notion_list_pages
Read-onlyIdempotent

List all accessible pages in your Notion workspace. Returns titles and IDs to discover available content.

Input Schema

NameRequiredDescriptionDefault
page_sizeNoNumber of results to return (default 10, max 100)
start_cursorNoPagination cursor for next page of results

Output Schema

NameRequiredDescriptionDefault
objectNoAlways 'list'
resultsNoArray of accessible pages
has_moreNoWhether more results exist
next_cursorNoPagination cursor for next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "has_more": {
+      "description": "Whether more results exist",
+      "type": "boolean"
+    },
+    "next_cursor": {
+      "description": "Pagination cursor for next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "object": {
+      "description": "Always 'list'",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of accessible pages",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Page ID",
+            "type": "string"
+          },
+          "object": {
+            "description": "Object type ('page')",
+            "type": "string"
+          },
+          "title": {
+            "description": "Page title content blocks",
+            "items": {
+              "properties": {
+                "text": {
+                  "properties": {
+                    "content": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "page_size": 10
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by specifying the output (titles and IDs) and scope ('all accessible pages'), which goes beyond annotations. Behavior is clearly safe and non-mutative.

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?

Single sentence, front-loaded with the core action and outcome. No redundant information; every word earns its place. Appropriate for a simple list tool.

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 low complexity, full annotations, and existence of output schema, the description adequately covers the tool's purpose and return value. Could mention pagination explicitly, but the schema covers it. Sibling tools are numerous but not described.

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 baseline is 3. Description does not add any parameter-specific context beyond what the schema already provides (pagination via page_size and start_cursor). No additional semantics are given.

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?

Description uses specific verb 'list' and resource 'pages', clearly stating it returns 'titles and IDs to discover available content'. It effectively distinguishes from sibling Notion tools like notion_get_page (single page) or notion_search (search across workspace).

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?

Description implies usage for initial workspace discovery ('to discover available content') but does not explicitly state when to use versus alternatives like notion_search or notion_query_database. No exclusions or alternative recommendations are provided.

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