Skip to main content
Glama
Hermoso

Hermoso

Official

List Notion pages

list_notion_pages
Read-onlyIdempotent

Find the Notion pages and databases shared with Hermoso by title, returning the IDs that save, append and read tools require. Read-only and free; requires a connected Notion account.

Instructions

Find the Notion pages and databases the user shared with Hermoso, by title, newest edited first. Gives the page id that save_to_notion, append_to_notion_page and read_notion_page take, or the database id to save rows into. 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": "list_notion_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNolimit results to pages or to databases; omit for both
limitNo1-100, default 25
queryNowords in the title
cursorNofrom the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / type / description
      Added value: +"limit results to pages or to databases; omit for both"
  2. Addedv0.1.454

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, yet the description adds materially new facts: it is free, it requires Notion to be connected via Connectors > Notion, results are limited to what the user shared, and ordering is newest-edited-first. The auth prerequisite in particular is actionable information the agent cannot get from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no filler. The core purpose and scope come first, then the downstream id usage and the connection prerequisite, so the agent gets the highest-value facts up front.

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?

There is no output schema, but the description compensates by stating what is returned (page ids and database ids) and how results are ordered and scoped. Combined with the annotated safety profile and the connection prerequisite, an agent has everything needed to call this correctly.

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 coverage is 100%, so the enum for type, the 1-100 limit range with default 25, and the cursor are all already documented in structured fields. The description only restates that title words drive the search ("by title") and implies truncation/ordering, adding little beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource ("Find the Notion pages and databases"), and adds distinguishing scope: only items the user shared with Hermoso, searched by title, sorted newest-edited-first. An agent can immediately tell this apart from list_linkedin_pages, query_notion_database, or read_notion_page.

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?

Explicitly routes the agent downstream: the returned page id feeds save_to_notion, append_to_notion_page and read_notion_page, and the database id is used to save rows. That is strong when-to-use context. It stops short of an explicit exclusion (e.g. use query_notion_database instead when you know the schema and want filtered rows), so it is not a full 5.

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