Skip to main content
Glama
Sign In
notion-private-api-mcp

notion-private-api-mcp

by kirvigen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Markdown To Blocks

markdown_to_blocks

Convert Markdown text into a simplified block JSON format for Notion API integration.

Instructions

Convert Markdown into the simplified block JSON format.

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": {
      "markdown": "<markdown>"
    },
    "name": "markdown_to_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYesMarkdown source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states 'convert'. It does not disclose whether the conversion is pure, if it validates markdown, or what happens on invalid input. No side effects or performance characteristics are mentioned.

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?

Description is a single, concise sentence with no filler. It is front-loaded with the essential purpose. For a simple conversion tool with one parameter, this level of conciseness is appropriate.

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

Completeness3/5

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

Given the low complexity (1 required param, no output schema, no nested objects), the description is minimally adequate. However, it lacks information about the output structure, error handling, and any constraints on the markdown input, which would be helpful for an agent to use the tool 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% for the single parameter 'markdown', with a basic description 'Markdown source.' The tool description adds the output format ('simplified block JSON'), which indirectly clarifies the input expectations but does not add extra detail like allowed markdown syntax.

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?

Description clearly states the tool converts markdown to a simplified block JSON format. The verb 'convert' and the resource 'Markdown' are specific, and the tool is distinct from sibling tools like append_blocks and create_page which deal with existing blocks or pages.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or when a different tool might be more appropriate, such as if the user already has blocks and needs to append them.

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