Tailprint

render_presentation

Convert Markdown slides separated by --- into a widescreen 16:9 vector PDF with slide numbers, themes, an inline cover preview, and a hosted PDF link.

Instructions

Converts Markdown slides (separated by "---") into a widescreen 16:9 presentation vector PDF (1920x1080) with slide numbers and modern Tailwind styling. Returns an inline cover preview and hosted PDF link.

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

Input Schema

Name	Required	Description	Default
`theme`	No	Slide theme: "dark", "midnight", "gradient", or "minimal" (default: "dark")	dark
`title`	No	Keynote or presentation title	Executive Briefing
`author`	No	Author or presenter name	Tailprint AI
`markdown`	Yes	Markdown text containing slides separated by "---". Use "# Title" for slide header, "## Subtitle", and bullet points.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the output contract: vector PDF, 1920x1080, slide numbers, Tailwind styling, inline cover preview plus hosted PDF link. It omits any mention of authentication, size limits, or how theme/title/author affect the rendered artifact.

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?

Two sentences, front-loaded with the core conversion and followed by the return shape. No redundant or filler wording.

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-parameter rendering tool with no output schema, the description explains both the rendering characteristics and the returned artifacts, which is enough to call it correctly. Only environment-level details (limits, auth) are absent.

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 description coverage is 100%, so every parameter including the theme enum is already documented in the schema. The description reinforces the "---" separator and slide syntax but adds no new meaning beyond that baseline.

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?

Names a specific transformation: Markdown slides separated by "---" into a 16:9 vector PDF at 1920x1080 with slide numbers. The input format and output specs make it distinguishable from a generic render_pdf, though no sibling is named explicitly.

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?

Usage is implied by the input requirement (Markdown with "---" separators) but there is no explicit when-to-use guidance, no when-not-to-use, and no pointer to render_pdf or render_template for other rendering needs.

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

Deploy Server