Skip to main content
Glama

databases

Manage Notion database schemas, query with filters and sorts, and perform bulk page operations like create, update, and delete.

Instructions

Database schema, query, and bulk row operations.

Actions (required params -> optional):

  • create (parent_id -> title, properties, is_inline, icon, cover)

  • get (database_id)

  • query (database_id -> filters, sorts, limit, search)

  • create_page (database_id, pages[{properties}])

  • update_page (database_id, page_id, page_properties)

  • delete_page (database_id, page_ids)

  • create_data_source / update_data_source / update_database / list_templates

Use pages instead for single page CRUD. Accepts both database_id (from URL) and data_source_id (from workspace search) -- auto-resolved.

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. "(icon)"), 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
Behavior2/5

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

The description lists actions including destructive ones like delete_page, but the annotation 'destructiveHint: false' contradicts this. The description does not clarify the contradiction or provide additional behavioral context beyond the schema.

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?

The description is well-structured with bullet points and clear groupings, but it is somewhat lengthy. It is front-loaded with the main purpose and each sentence provides useful information.

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?

Given the tool's complexity (18 parameters, multiple actions, nested objects), the description is comprehensive. It covers all actions, explains ID resolution, provides examples for icon and cover, and references sibling tool for single page operations, leaving no obvious gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, baseline is 3. The description adds value by summarizing required and optional parameters for each action (e.g., 'create (parent_id -> title, properties, ...)') and explaining icon/cover formats in detail, exceeding 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 clearly states the tool's purpose as database schema, query, and bulk row operations, listing all actions. It explicitly distinguishes itself from the sibling tool 'pages' for single page CRUD, providing clear differentiation.

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?

The description provides a specific alternative ('Use pages instead for single page CRUD') and explains auto-resolution of database_id/data_source_id. However, it does not give detailed guidance on when to use each action or when not to use the tool.

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