Skip to main content
Glama
Hermoso

Hermoso

Official

Add to a Notion page

append_to_notion_page

Add markdown, swipefile collections, or scheduled posts to the end of an existing Notion page without altering its current content.

Instructions

Add to the END of an existing Notion page (pageId or its link, from list_notion_pages): markdown content, a swipefileCollection, or includeSchedule:true. Nothing already on the page changes. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageId": "<pageId>"
    },
    "name": "append_to_notion_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYespage id or link
contentNomarkdown to add
includeScheduleNotrue appends the scheduled posts too
swipefileCollectionNoswipefile collection name or id to append, with each ad's creative, copy, dates and link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.465
    • addedInput schema / properties / includeSchedule / description
      Added value: +"true appends the scheduled posts too"
    • addedInput schema / properties / swipefileCollection / description
      Added value: +"swipefile collection name or id to append, with each ad's creative, copy, dates and link"
  2. Addedv0.1.454

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=true. The description reinforces these with 'Nothing already on the page changes' and adds the cost signal ('Free'), which are useful beyond the annotations. Return behavior isn't described, but with no output schema that omission is minor.

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?

Front-loads the core action, then the modes, then the non-destructiveness and cost. Dense with zero wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-param write tool with a fully covered schema and clear annotations, the description conveys scope, non-destructiveness, source of pageId, and cost. It doesn't describe the response, but with no output schema that's an acceptable gap.

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 baseline is 3. The description adds real value by indicating pageId's source ('from list_notion_pages') and framing the three optional modes; the swipefile detail largely restates the schema, so it doesn't rise to a 5.

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?

States a specific verb (Add/append), resource (existing Notion page), and scope (to the END). The 'Nothing already on the page changes' clause distinguishes it from a save/overwrite operation like save_to_notion, and the three append modes are enumerated.

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?

Tells the agent where pageId comes from (from list_notion_pages) and what can be appended (markdown, swipefileCollection, includeSchedule). Clear usage context, but it doesn't explicitly name alternatives like save_to_notion or state when not to use it.

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