Skip to main content
Glama
Hermoso

Hermoso

Official

Export the schedule to Notion

export_schedule_to_notion

Export a posting schedule to a Notion database as one row per post, including date, channels, caption, media link, and status; create a new database or write into an existing one.

Instructions

Export the posting schedule to a Notion database, one row per post: date, channels, caption, media link and status. Creates a new database (under parentPageId, or private in the workspace) or writes into an existing one (databaseId), matching its columns by name. historyDays adds posts already published. Up to 100 rows per run; the answer says if more were left. Free.

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

Input Schema

NameRequiredDescriptionDefault
titleNoname for a new database
databaseIdNoan existing database id or link
historyDaysNo0-90 days of published posts to include
dataSourceIdNodata source id of an existing database to write rows into, matched to columns by name
parentPageIdNoNotion page to create the new database under; omit for a private page in the workspace

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 of an existing database to write rows into, matched to columns by name"
    • addedInput schema / properties / parentPageId / description
      Added value: +"Notion page to create the new database under; omit for a private page in the workspace"
  2. Addedv0.1.454

TDQS

A4.4/5.0
Behavior5/5

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

Adds material context beyond the annotations: column matching by name, the 100-row cap, a signal that the response says if more rows were left, and cost ('Free'). Those are real behavioral and operational facts an agent needs, and they align with readOnlyHint=false and openWorldHint=true.

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 what the export produces, then covers the create/write modes, history scope, row cap, and cost in densely packed sentences. No filler; every sentence carries an operational fact.

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 5-param, open-world, non-read-only export with no output schema, the description covers modes, limits, output fields, and cost. An agent could invoke it correctly without reading 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 baseline is 3, but the description clarifies the create-vs-write distinction for parentPageId/databaseId and the meaning of historyDays. dataSourceId is only indirectly covered via 'matching its columns by name', so it isn't fully fleshed out beyond the schema.

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?

States a specific verb ('Export') and resource ('the posting schedule to a Notion database'), plus the row shape (date, channels, caption, media link, status). That makes it distinguishable from generic siblings like save_to_notion or append_to_notion_page by scope, though it never names an alternative explicitly.

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 the two operating modes clearly: create a new database under parentPageId (or private), or write into an existing one via databaseId. Also clarifies that historyDays includes already-published posts and that only 100 rows run at a time. No explicit when-not or sibling routing, which keeps it from 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