Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

pdf_to_epub

Convert a PDF document to EPUB ebook format. Supports automatic chapter detection, image extraction (Pro), and custom chapter grouping.

Free tier supports up to 10MB per PDF. Pro ($9/mo) is strongly recommended for PDF conversion — the 30MB limit handles most scanned or illustrated PDFs. Upgrade at https://epublys.com/pricing

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": {
      "file": "<file>"
    },
    "name": "pdf_to_epub"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBase64-encoded PDF file content
nameNoOriginal filename — the output is named after its stem (e.g. "Book.epub" gives "Book (compressed).epub"); without it the output keeps a fixed name
languageNoLanguage code for the output EPUBen
chapterModeNoHow to split into chaptersauto
extractImagesNoPro only — ignored on free tier
pagesPerChapterNoPages per chapter (only for every-n mode)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 material constraints: per-file size limits, that extractImages is silently ignored on free tier, and that Pro raises the ceiling to 30MB. It still omits what the tool returns (file bytes vs URL) and how uploads are retained, which matters for a file-upload operation.

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?

Purpose is front-loaded in the first sentence and the useful limits follow. The closing 'Upgrade at https://epublys.com/pricing' line is promotional rather than operational, but it is short and does convey the upgrade path referenced earlier.

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?

For a six-parameter file-conversion tool with no annotations and no output schema, the description should say what the caller gets back (base64 EPUB, URL, or stored artifact). It also never mentions error conditions for oversized or unsupported PDFs, leaving the agent guessing at failure handling.

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%, so every one of the six parameters is already documented in the schema, including the Pro-only caveat on extractImages and the every-n condition on pagesPerChapter. The description adds nothing parameter-level beyond that, which is the baseline-3 case.

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 pair ('Convert a PDF document to EPUB ebook format') and the format naming distinguishes it implicitly from docx_to_epub and epub_to_pdf. The follow-on sentence adds the conversion capabilities (chapter detection, image extraction, chapter grouping) that define what the conversion actually produces.

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?

Gives a concrete size threshold for the free tier (10MB) and states Pro is 'strongly recommended for PDF conversion', which is real selection context. However, it never contrasts with sibling tools such as docx_to_epub or markdown_to_epub, and the Pro guidance points at upgrade_to_pro without naming it.

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

All Epublys toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources