Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_create_database

Destructive

Creates a Notion database under a page, with one data source and that data source's property schema. The schema is a map of property name to type, for example {"Task": "title", "Due": "date", "Stage": {"type": "status", "options": ["Todo", "Done"]}}. A map with no title property gets one named Name. Returns the database's id, title, url, parent, is_inline and data_sources (their ids are what notion_create_page and notion_query_data_source take).

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": {
      "parent_page_id": "<parent_page_id>"
    },
    "name": "notion-mcp__notion_create_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe database's title as plain text. Over 2,000 characters is split into several text pieces; the limit is 200,000.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
is_inlineNotrue shows the database inside the parent page's content; false (the default) makes it a full-page database.
propertiesNoProperty name to type. A type is a name (title, rich_text, number, select, multi_select, status, date, people, files, checkbox, url, email, phone_number, created_time, created_by, last_edited_time, last_edited_by, place, verification, unique_id) or an object with settings: {"type": "select", "options": ["A", {"name": "B", "color": "red"}]}, {"type": "number", "format": "dollar"}, {"type": "formula", "expression": "..."}, {"type": "relation", "data_source_id": "...", "dual": true}, {"type": "unique_id", "prefix": "T"}. Any type also takes "description", and "config" with Notion's own settings object (the form a rollup takes).
descriptionNoThe database's description as plain text.
parent_page_idYesThe page the database is created in: its Notion id or URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=false and destructiveHint=true, so the safety profile is covered. The description contributes real behavioral detail beyond that: the automatic 'Name' title property when no title is supplied, and an explicit enumeration of the returned object (id, title, url, parent, is_inline, data_sources) compensating for the absent output schema. It does not explain why a create operation is flagged destructive or what permissions are required, which leaves a small gap.

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?

Three sentences, front-loaded with purpose and scope, then the input contract, then the return contract. Every sentence carries information, though the embedded property-map example is fairly heavy and overlaps with what the schema already spells out.

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 nested-object mutation tool with a single required parameter and no output schema, the description covers the essential ground: what gets created alongside the database, how the property map is shaped, the default title behavior, and exactly which fields come back and how they feed the sibling tools. Combined with full schema coverage, an agent has enough to call it correctly.

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% and every parameter (title, account, is_inline, properties, description, parent_page_id) is documented in the schema itself, so the baseline of 3 applies. The description's worked property-map example ('Task': 'title', 'Due': 'date', 'Stage': {...}) largely restates the schema's already detailed properties documentation rather than adding new meaning.

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 opens with a specific verb and resource ('Creates a Notion database under a page') and adds the crucial scope detail that it also creates one data source plus that data source's property schema. This distinguishes it cleanly from siblings like notion_update_data_source, notion_get_database and notion_create_page.

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 only implied: the reader can infer this is the creation step that must precede notion_query_data_source or notion_create_page, since the description notes their ids come from this call's output. There is no explicit when-to-use/when-not-to-use guidance or statement of prerequisites, such as needing an existing parent page or integration access.

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

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