Skip to main content
Glama
ai-aviate

better-mcp-notion

by ai-aviate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list

Retrieve Notion database records as a Markdown table or show child pages of a page. Filter and sort results by property expressions for targeted views.

Instructions

List database records as a Markdown table, or list child pages of a page.

For databases: returns a table with properties as columns. For pages: returns a numbered list of child pages.

You can pass a database/page name (resolved via search) or an ID/URL.

Filter syntax (databases only)

Simple expressions matched against DB property names and types:

  • "Status is Done" → select/status equals

  • "Priority = High" → select equals

  • "Tags contains backend" → multi_select contains

  • "Done is true" → checkbox equals

  • "Due Date after 2026-03-01" → date after

  • "Score > 80" → number greater_than

  • "Name contains API" → title/rich_text contains Multiple filters: separate with " AND " (e.g. "Status is Done AND Priority is High")

Sort syntax (databases only)

  • "Due Date ascending" or "Due Date asc"

  • "Created descending" or "Created desc"

Example output

Task Board (24 items)

Name

Status

Due Date

Fix login bug

In Progress

2026-03-01

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort expression (e.g. "Due Date ascending", "Created desc")
limitNoMax items to return (default: 50)
filterNoFilter expression (e.g. "Status is Done", "Priority > 3"). See tool description for syntax.
targetYesDatabase or page: name (e.g. 'Task Board'), ID, or Notion URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format, provides an example output, explains name resolution via search, and gives detailed filter/sort semantics. This goes well beyond what the tool name alone implies.

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 appropriately organized with headers and examples. The main behavior is front-loaded, and the length is justified by the complexity of the filter/sort syntax. No sentence feels wasted.

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 list operation with no output schema, the description supplies return formats, an example table, target resolution rules, and enough syntax detail to construct valid filters and sorts. There is no critical gap preventing an agent from calling the tool correctly.

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

Parameters5/5

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

Although the schema already documents all four parameters, the description adds essential meaning: a full filter expression grammar, sort syntax, and target resolution behavior. The schema even references the tool description for filter syntax, making this added detail necessary for correct invocation.

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 first sentence clearly states the action (list) and the two concrete resource types: database records as a Markdown table and child pages as a numbered list. It is unambiguous about what the tool does, though it does not explicitly name sibling tools like read/search to draw the boundary.

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 explains when to use each mode (databases vs pages), how targets are resolved via search, and how to construct filter and sort expressions. It does not explicitly say 'use read for page content' or 'use search to find targets,' but the context is clear enough for an agent to invoke it correctly.

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