Skip to main content
Glama

Notion_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Notion Get Database

notion_get_database
Read-onlyIdempotent

Get a Notion database schema by ID. Returns all properties, field types, and configuration to understand structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesNotion database ID (UUID format, with or without dashes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDatabase ID
urlNoNotion web URL for the database
titleNoDatabase title content blocks
objectNoObject type ('database')
parentNoParent object reference
archivedNoWhether database is archived
created_byNoCreator user object
propertiesNoDatabase properties and their configurations
descriptionNoDatabase description content blocks
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 database 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"
+    },
+    "description": {
+      "description": "Database description content blocks",
+      "type": "array"
+    },
+    "id": {
+      "description": "Database 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 ('database')",
+      "type": "string"
+    },
+    "parent": {
+      "description": "Parent object reference",
+      "type": "object"
+    },
+    "properties": {
+      "description": "Database properties and their configurations",
+      "type": "object"
+    },
+    "title": {
+      "description": "Database title content blocks",
+      "items": {
+        "properties": {
+          "text": {
+            "properties": {
+              "content": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "Notion web URL for the database",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "database_id": "a1b2c3d4e5f641d4a716446655440000"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds mild context about return content but no additional behavioral traits like error handling or rate limits.

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 key action, no wasted words.

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 one parameter, rich annotations, and output schema present, the description sufficiently explains the tool's purpose and return content without gaps.

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 the schema already documents the only parameter. The description adds no new parameter meaning beyond 'by ID'.

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?

Describes a specific verb and resource ('Get Notion database schema by ID'), clearly distinguishing it from sibling tools like notion_query_database by focusing on schema, properties, field types, and configuration.

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?

Implies usage for understanding database structure, but does not explicitly state when to avoid or mention alternatives. Still clear enough given the tool name and context.

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