Skip to main content
Glama
Hermoso

Hermoso

Official

Read a Notion database

query_notion_database
Read-onlyIdempotent

Read and filter rows from a shared Notion database, including properties, links, and column types, to import calendars or locate records for updates.

Instructions

Read the ROWS of a Notion database the user shared with Hermoso — e.g. the team's content calendar: each row's title, id, link and every property as a plain value (status, date, channels, caption, links), plus the database's columns with their types and options. Filter with match {"Status": "Scheduled"} (typed from the database's own columns) or a raw Notion filter object; sort with sortBy (a column, or created_time / last_edited_time) and direction. Up to 100 rows per call, cursor for more; the answer says when Notion stopped at its 10,000-result limit. Use it to import a calendar and schedule its posts, or to find the row update_notion_row changes. Read-only, free. Needs Notion connected (Connectors > Notion).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_notion_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-100, default 50
matchNo{"Column": value} — equality for status/select/checkbox/number/date, contains for text/multi-select
cursorNonextCursor from the previous page of rows
filterNoa raw Notion filter object
sortByNocolumn name to sort by, or created_time or last_edited_time
archivedNoread archived rows instead
directionNoascending (default) or descending
databaseIdNodatabase id or link (list_notion_pages type:"database")
dataSourceIdNodata source id from an earlier read, as an alternative to databaseId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.465

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, and the description adds substantial context on top: 100 rows per call, cursor-based paging, an explicit notice when Notion stops at its 10,000-result limit, and the Connectors > Notion connection requirement. Nothing here contradicts the annotations.

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?

Purpose and return shape are front-loaded in the first sentence, with filtering, sorting, pagination, use cases, and prerequisites following in a logical order. The dense single paragraph is largely earned content, though it packs enough clauses that scannability suffers slightly.

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?

For a 9-parameter tool with nested objects and no output schema, the description supplies the missing return-value contract (row fields, column types and options) along with pagination limits and the auth prerequisite. An agent has enough to call it correctly without inspecting anything further.

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?

Schema coverage is 100%, so the schema carries the baseline, but the description adds real meaning: a worked match example ({"Status": "Scheduled"}) that is typed from the database's own columns, the sortBy alternatives including created_time and last_edited_time, and the direction/limit interplay. It stops short of explaining filter-object semantics or the databaseId vs dataSourceId choice.

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 opens with a specific verb-plus-resource ('Read the ROWS of a Notion database') and immediately enumerates the returned shape: each row's title, id, link, and every property, plus the database's columns with types and options. It also distinguishes itself from mutation sibling update_notion_row, which it names as the tool for changing the row this one finds.

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?

It gives two concrete use cases ('import a calendar and schedule its posts' and 'find the row update_notion_row changes') plus the prerequisite that Notion must be connected. It lacks an explicit exclusion such as when to prefer read_notion_page for a single page, so it is clear context rather than a full decision rule.

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

Deploy Server

Other Tools