Skip to main content
Glama

update-database

Modify an existing Notion database by updating its title, description, or property schema to reflect changes in your workspace structure.

Instructions

Update an existing database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesID of the database to update
titleNoOptional new title as rich text array
descriptionNoOptional new description as rich text array
propertiesNoOptional updated properties schema

Implementation Reference

  • Handler function for the 'update-database' tool within the tools/call request handler. Destructures arguments, builds update parameters conditionally, calls notion.databases.update, and returns the response as text content.
    else if (name === "update-database") {
      const { database_id, title, description, properties } = args;
      
      const updateParams = {
        database_id,
      };
    
      if (title !== undefined) {
        updateParams.title = title;
      }
    
      if (description !== undefined) {
        updateParams.description = description;
      }
    
      if (properties !== undefined) {
        updateParams.properties = properties;
      }
    
      const response = await notion.databases.update(updateParams);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'update-database' tool, returned in the tools/list response. Specifies parameters like database_id (required), title, description, properties.
    {
      name: "update-database",
      description: "Update an existing database",
      inputSchema: {
        type: "object",
        properties: {
          database_id: {
            type: "string",
            description: "ID of the database to update"
          },
          title: {
            type: "array",
            description: "Optional new title as rich text array"
          },
          description: {
            type: "array",
            description: "Optional new description as rich text array"
          },
          properties: {
            type: "object",
            description: "Optional updated properties schema"
          }
        },
        required: ["database_id"]
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Update' implies a mutation, but it doesn't disclose permission requirements, whether changes are reversible, side effects on related data, or error conditions. For a write operation with zero annotation coverage, this leaves critical behavioral traits unspecified.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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

Completeness2/5

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

Given the complexity of updating a database (a mutation with nested objects and no output schema), the description is insufficient. It lacks details on what 'update' entails—such as partial vs. full updates, validation rules, or response format—leaving the agent with incomplete context for safe and effective use.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond implying that updates apply to 'an existing database', which is already clear from the schema's 'database_id' parameter. This meets the baseline for high schema coverage.

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 the action ('Update') and target resource ('an existing database'), making the purpose immediately understandable. It distinguishes from siblings like 'create-database' (creation vs. update) and 'list-databases' (read vs. write), though it doesn't explicitly differentiate from other update tools like 'update-block' or 'update-page'.

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 doesn't mention prerequisites (e.g., needing a database_id), exclusions, or comparisons to siblings like 'update-page' or 'create-database'. The agent must infer usage from the name and schema alone.

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/Sjotie/notionMCP'

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