Skip to main content
Glama

databases

Manage Notion databases by creating, querying, and updating pages and schemas. Perform operations like filtering, sorting, and bulk edits to organize and manipulate structured data.

Instructions

Database operations: create, get, query, create_page, update_page, delete_page, create_data_source, update_data_source, update_database, list_templates. Accepts both database_id (from URL) and data_source_id (from workspace search) — auto-resolved. Databases contain data sources with schema and rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
database_idNoDatabase ID (from Notion URL) or data_source_id (from workspace search). Auto-resolved for query/create_page/list_templates.
data_source_idNoData source ID (for update_data_source action)
parent_idNoParent page ID (for create/update_database)
titleNoTitle (for database or data source)
descriptionNoDescription
propertiesNoSchema properties (for create/update data source)
is_inlineNoDisplay as inline (for create/update_database)
iconNoIcon (for update_database): emoji (e.g. "📋"), external URL (https://...), or built-in shorthand (name:color, e.g. "document:gray")
coverNoCover image (for update_database): URL or built-in shorthand (gradient_1..11, solid_red/yellow/blue/beige, nasa_*, met_*, rijksmuseum_*, woodcuts_*)
filtersNoQuery filters (for query action)
sortsNoQuery sorts
limitNoMax query results
searchNoSmart search across text fields (for query)
page_idNoSingle page ID (for update_page)
page_idsNoMultiple page IDs (for delete_page)
page_propertiesNoPage properties to update (for update_page)
pagesNoArray of pages for bulk create/update
Behavior3/5

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

The description adds some behavioral context beyond annotations, explaining the auto-resolution feature for database_id/data_source_id and clarifying that 'databases contain data sources with schema and rows.' However, annotations already cover basic safety (readOnlyHint=false, destructiveHint=false), and the description doesn't provide important behavioral details like rate limits, authentication requirements, or error handling for this multi-action tool.

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

Conciseness3/5

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

The description is reasonably concise but could be better structured. The first sentence lists 10 actions without grouping or prioritization, making it somewhat overwhelming. The second sentence about auto-resolution is helpful, but the final sentence about databases containing data sources feels tacked on rather than integrated into a coherent narrative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 18 parameters, multiple actions, and no output schema, the description provides basic orientation but lacks depth. It identifies the scope (database operations) and mentions auto-resolution, but doesn't explain the relationships between different actions, provide examples of common workflows, or clarify what 'auto-resolved' means in practice. Given the tool's complexity, more contextual guidance would be helpful.

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?

With 100% schema description coverage, the input schema already documents all 18 parameters thoroughly. The description adds minimal parameter semantics, only clarifying the auto-resolution behavior for database_id/data_source_id. This meets the baseline expectation when schema coverage is complete, but doesn't provide additional parameter context beyond what's already in the structured 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?

The description clearly states this is for 'Database operations' and lists 10 specific actions (create, get, query, etc.), providing a comprehensive overview of what the tool does. However, it doesn't explicitly differentiate this from sibling tools like 'pages' or 'blocks', which might also handle some database-related operations in Notion's ecosystem.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions auto-resolution of database_id/data_source_id for certain actions, but doesn't explain when to choose this tool over sibling tools like 'pages' or 'workspace' for database-related tasks. No explicit when/when-not guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/n24q02m/better-notion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server