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"]
      }
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update an existing database' implies a mutation operation, but it doesn't disclose any behavioral traits: no information about permissions required, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise at just three words: 'Update an existing database.' It's front-loaded with the core action and resource. There's zero wasted language or unnecessary elaboration. While it may be too brief for completeness, it earns full marks for conciseness.

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 this is a mutation tool (update operation) with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, what side effects occur, or any behavioral context. The description alone is insufficient for an agent to understand how to properly use this tool beyond the basic action implied by the name.

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 input schema already fully documents all four parameters (database_id, description, properties, title) with their types and descriptions. The tool description adds no additional meaning about parameters beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update an existing database' clearly states the verb (update) and resource (database), but it's vague about what specifically gets updated. It doesn't distinguish this tool from sibling tools like update-block or update-page, which also perform updates on different resources. The purpose is understandable but lacks specificity.

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. With sibling tools like update-block, update-page, and create-database available, there's no indication of when this tool is appropriate versus those other update/create operations. The agent must infer usage from the tool name alone.

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