Epublys

epub_to_pdf

Convert an EPUB ebook to PDF. Supports page size, margins, font, and page number options.

Pro ($9/mo) is strongly recommended for PDF conversion — the 30MB limit handles illustrated or academic books that exceed the free 5MB cap. 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": "epub_to_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes	Base64-encoded EPUB file content
`name`	No	Original filename — the output is named after its stem (e.g. "Book.epub" gives "Book (compressed).epub"); without it the output keeps a fixed name
`margins`	No	Page margins in points
`fontSize`	No	Font size in points
`pageSize`	No		a4
`fontFamily`	No		serif
`pageNumbers`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it delivers one genuinely useful behavioral fact: file size limits and the paid tier required for larger books. It omits other traits an agent needs, such as whether conversion is synchronous, what the response contains, and how failures are surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, which is good, but the second paragraph is promotional upsell copy with a URL and pricing pitch that dilutes the operational content, even if the size-cap detail inside it has some value.

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 7-parameter tool with no annotations and no output schema, the description should clarify the return shape (Base64 payload vs. link) and the base64 input expectation for 'file'. It covers conversion intent and size limits but leaves the output contract entirely unspecified.

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 57%, and the description only echoes the option categories (page size, margins, font, page numbers) that the schema already defines with enums, defaults, and ranges. It adds no format details, units, or interactions beyond what the schema provides.

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?

The first sentence states a specific verb and resource pair: 'Convert an EPUB ebook to PDF,' and names the option categories. It distinguishes itself from siblings like epub_to_markdown or pdf_to_epub implicitly through the conversion direction, though it never explicitly names an alternative.

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 context is implied by the format pair, and the description does disclose the 5MB free / 30MB Pro size threshold, which is a real gating condition. However, there is no explicit when-to-use/when-not guidance and no routing to sibling tools such as compress_epub for oversized files.

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

All Epublys tools Inspect

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.