yt-summarizer

create_notion_page

Creates a Notion page with a summarized YouTube transcript. Automatically saves it under the configured parent page.

Instructions

Create a new Notion page under the configured parent page.

Args: notion_page_content: A Notion "create page" API payload (properties + children blocks). The parent page ID is injected automatically from PARENT_PAGE_ID.

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": {
      "notion_page_content": "<notion_page_content>"
    },
    "name": "create_notion_page"
  }
}

Input Schema

Name	Required	Description	Default
`notion_page_content`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of transparency. It discloses a useful behavior: 'The parent page ID is injected automatically from PARENT_PAGE_ID.' However, it does not mention permissions, error conditions, or the fact that it is a write operation beyond the name itself, leaving some gaps.

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 tightly written with a single opening sentence and an 'Args' section. It avoids redundancy and front-loads the core function, making it easy to scan and understand.

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 tool with one parameter and an output schema, the description covers essential details: the payload type, the automatic parent injection, and the overall purpose. It lacks explicit usage guidance, but the simplicity of the tool and presence of an output schema make this less critical.

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?

The schema provides no description for the parameter, and schema coverage is 0%. The description compensates by explaining that 'notion_page_content' is a Notion 'create page' API payload with 'properties + children blocks' and that the parent ID is auto-injected. This adds meaning beyond the bare schema definition.

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?

The description clearly states the tool's function: 'Create a new Notion page under the configured parent page.' It uses a specific verb and resource, and the sibling tool 'get_transcript' contrasts as a read operation, making the purpose distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating the action, but it does not explicitly say when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The parent page injection is noted, but there is no directive like 'use this when you need to add a page.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server