Skip to main content
Glama

query-database

Retrieve and organize data from Notion databases using customizable filters, sorting, and pagination to efficiently manage and analyze information.

Instructions

Query a database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesID of the database to query
filterNoOptional filter criteria
page_sizeNoNumber of results per page
sortsNoOptional sort criteria
start_cursorNoOptional cursor for pagination

Implementation Reference

  • Handler for the 'query-database' tool. Destructures arguments, builds query parameters for Notion's databases.query API (including optional filter, sorts, pagination), calls the API, and returns the response as text content.
    else if (name === "query-database") {
      console.error("Query database handler called with:", JSON.stringify(args, null, 2));
      const { database_id, filter, sorts, start_cursor, page_size } = args;
      
      const queryParams = {
        database_id,
        page_size: page_size || 100,
      };
    
      if (filter) queryParams.filter = filter;
      if (sorts) queryParams.sorts = sorts;
      if (start_cursor) queryParams.start_cursor = start_cursor;
    
      const response = await notion.databases.query(queryParams);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Tool definition in tools/list response, including name, description, and detailed inputSchema specifying parameters for querying a Notion database.
      name: "query-database",
      description: "Query a database",
      inputSchema: {
        type: "object",
        properties: {
          database_id: {
            type: "string",
            description: "ID of the database to query"
          },
          filter: {
            type: "object",
            description: "Optional filter criteria"
          },
          sorts: {
            type: "array",
            description: "Optional sort criteria"
          },
          start_cursor: {
            type: "string",
            description: "Optional cursor for pagination"
          },
          page_size: {
            type: "number",
            description: "Number of results per page",
            default: 100
          }
        },
        required: ["database_id"]
      }
    },
  • server.js:37-313 (registration)
    The tools/list request handler that registers/declares all available tools including 'query-database' with their schemas.
    server.setRequestHandler(z.object({
      method: z.literal("tools/list")
    }), async () => {
      return {
        tools: [
          {
            name: "list-databases",
            description: "List all databases the integration has access to",
            inputSchema: {
              type: "object",
              properties: {}
            }
          },
          {
            name: "query-database",
            description: "Query a database",
            inputSchema: {
              type: "object",
              properties: {
                database_id: {
                  type: "string",
                  description: "ID of the database to query"
                },
                filter: {
                  type: "object",
                  description: "Optional filter criteria"
                },
                sorts: {
                  type: "array",
                  description: "Optional sort criteria"
                },
                start_cursor: {
                  type: "string",
                  description: "Optional cursor for pagination"
                },
                page_size: {
                  type: "number",
                  description: "Number of results per page",
                  default: 100
                }
              },
              required: ["database_id"]
            }
          },
          {
            name: "create-page",
            description: "Create a new page in a database",
            inputSchema: {
              type: "object",
              properties: {
                parent_id: {
                  type: "string",
                  description: "ID of the parent database"
                },
                properties: {
                  type: "object",
                  description: "Page properties"
                },
                children: {
                  type: "array",
                  description: "Optional content blocks"
                }
              },
              required: ["parent_id", "properties"]
            }
          },
          {
            name: "update-page",
            description: "Update an existing page",
            inputSchema: {
              type: "object",
              properties: {
                page_id: {
                  type: "string",
                  description: "ID of the page to update"
                },
                properties: {
                  type: "object",
                  description: "Updated page properties"
                },
                archived: {
                  type: "boolean",
                  description: "Whether to archive the page"
                }
              },
              required: ["page_id", "properties"]
            }
          },
          {
            name: "create-database",
            description: "Create a new database",
            inputSchema: {
              type: "object",
              properties: {
                parent_id: {
                  type: "string",
                  description: "ID of the parent page"
                },
                title: {
                  type: "array",
                  description: "Database title as rich text array"
                },
                properties: {
                  type: "object",
                  description: "Database properties schema"
                },
                icon: {
                  type: "object",
                  description: "Optional icon for the database"
                },
                cover: {
                  type: "object",
                  description: "Optional cover for the database"
                }
              },
              required: ["parent_id", "title", "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"]
            }
          },
          {
            name: "get-page",
            description: "Retrieve a page by its ID",
            inputSchema: {
              type: "object",
              properties: {
                page_id: {
                  type: "string",
                  description: "ID of the page to retrieve"
                }
              },
              required: ["page_id"]
            }
          },
          {
            name: "get-block-children",
            description: "Retrieve the children blocks of a block",
            inputSchema: {
              type: "object",
              properties: {
                block_id: {
                  type: "string",
                  description: "ID of the block (page or block)"
                },
                start_cursor: {
                  type: "string",
                  description: "Cursor for pagination"
                },
                page_size: {
                  type: "number",
                  description: "Number of results per page",
                  default: 100
                }
              },
              required: ["block_id"]
            }
          },
          {
            name: "append-block-children",
            description: "Append blocks to a parent block",
            inputSchema: {
              type: "object",
              properties: {
                block_id: {
                  type: "string",
                  description: "ID of the parent block (page or block)"
                },
                children: {
                  type: "array",
                  description: "List of block objects to append"
                },
                after: {
                  type: "string",
                  description: "Optional ID of an existing block to append after"
                }
              },
              required: ["block_id", "children"]
            }
          },
          {
            name: "update-block",
            description: "Update a block's content or archive status",
            inputSchema: {
              type: "object",
              properties: {
                block_id: {
                  type: "string",
                  description: "ID of the block to update"
                },
                block_type: {
                  type: "string",
                  description: "The type of block (paragraph, heading_1, to_do, etc.)"
                },
                content: {
                  type: "object",
                  description: "The content for the block based on its type"
                },
                archived: {
                  type: "boolean",
                  description: "Whether to archive (true) or restore (false) the block"
                }
              },
              required: ["block_id", "block_type", "content"]
            }
          },
          {
            name: "get-block",
            description: "Retrieve a block by its ID",
            inputSchema: {
              type: "object",
              properties: {
                block_id: {
                  type: "string",
                  description: "ID of the block to retrieve"
                }
              },
              required: ["block_id"]
            }
          },
          {
            name: "search",
            description: "Search Notion for pages or databases",
            inputSchema: {
              type: "object",
              properties: {
                query: {
                  type: "string",
                  description: "Search query string",
                  default: ""
                },
                filter: {
                  type: "object",
                  description: "Optional filter criteria"
                },
                sort: {
                  type: "object",
                  description: "Optional sort criteria"
                },
                start_cursor: {
                  type: "string",
                  description: "Cursor for pagination"
                },
                page_size: {
                  type: "number",
                  description: "Number of results per page",
                  default: 100
                }
              }
            }
          }
        ]
      };
    });
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is read-only, has side effects, requires permissions, involves rate limits, or describes output format. For a query tool with 5 parameters, this is a significant gap in transparency.

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 waste. It's appropriately sized and front-loaded, though it lacks detail. Every word earns its place, making it highly concise.

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 5 parameters, nested objects, no output schema, and no annotations, the description is incomplete. It doesn't explain what the tool returns, how queries are structured, or behavioral traits. For a complex query tool, this leaves critical gaps for an agent.

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 documented in the schema. The description adds no meaning beyond the schema—it doesn't explain query semantics, filter/sort formats, or pagination behavior. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Query a database' states the basic action (query) and resource (database), which is clear but vague. It doesn't specify what type of query (e.g., SQL, NoSQL, filtered retrieval) or distinguish from siblings like 'search' or 'list-databases'. This provides minimal viable information without differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'search' or 'list-databases'. The description implies general querying but doesn't specify contexts, prerequisites, or exclusions. This leaves the agent without direction on tool selection.

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

Related 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/emmanuelsystems/mcpnotionslack'

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