Skip to main content
Glama
Hermoso

Hermoso

Official

Save to Notion

save_to_notion

Create a new Notion page from markdown reports, swipefile collections, or content calendars, placing it under a parent page or database row.

Instructions

Save to the user's Notion as a NEW page: a research report, competitor teardown or campaign report as content (markdown: headings, lists, links, and an image or video URL on its own line becomes the media), a swipefile collection (swipefileCollection: name or id; each ad with its creative, copy, run dates and link), the content calendar (includeSchedule:true), or a mix. Put it under parentPageId, as a row in databaseId, or omit both for a private page in their workspace. Long text is split across blocks, never cut. The answer is read back from Notion. Free; never overwrites anything.

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": "save_to_notion"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoone emoji
titleNotitle of the new Notion page
contentNomarkdown body
databaseIdNodatabase id or link: saves as a new row
dataSourceIdNodata source id to save into as a new row; pass only one of parentPageId, databaseId, dataSourceId
parentPageIdNopage id or link to save under
includeScheduleNoadd the scheduled posts
swipefileCollectionNoswipefile collection name or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.465
    • addedInput schema / properties / dataSourceId / description
      Added value: +"data source id to save into as a new row; pass only one of parentPageId, databaseId, dataSourceId"
    • addedInput schema / properties / title / description
      Added value: +"title of the new Notion page"
  2. Addedv0.1.454

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world behavior; the description adds real value on top by stating 'never overwrites anything', 'Long text is split across blocks, never cut', that the result is read back from Notion, and that the call is free. It does not cover auth/permission requirements or rate limits, so it is strong but not exhaustive.

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?

The core action and destination logic are front-loaded, and each clause carries information about a distinct payload type. The single dense paragraph is slightly run-on, but there is little filler.

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?

With 8 optional parameters, no output schema, and mutation semantics, the description covers destination selection, content encoding, and overwrite behavior adequately, and it gestures at the return ('The answer is read back from Notion'). Return shape and failure behavior remain thin, keeping it below 5.

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 earns above baseline by explaining markdown handling in `content` (headings, lists, links, and a standalone image/video URL becoming media) and by characterizing swipefileCollection and includeSchedule. It does not clarify the mutual exclusivity of parentPageId/databaseId/dataSourceId beyond what the schema says.

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 and resource ('Save to the user's Notion as a NEW page') and enumerates the concrete payload types it accepts (research report, competitor teardown, campaign report, swipefile collection, content calendar). The emphasis on NEW page distinguishes it from append_to_notion_page and export_schedule_to_notion among the siblings.

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?

Explains how to choose the destination (parentPageId, databaseId, or omit both for a private workspace page) and when to set includeSchedule. It gives clear usage context but never names a sibling and says 'use X instead' or states when-not-to-use, so it falls short of a 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