Skip to main content
Glama
Sign In

Epublys

by com.epublys
OverviewDiscussionsAdmin

epub_to_markdown

Convert an EPUB ebook to Markdown. Returns a ZIP with one Markdown file per chapter (YAML frontmatter with title/book/author/chapter), an index.md with book metadata and a linked table of contents, and the referenced images. Plain CommonMark — drops straight into an Obsidian vault or any notes pipeline.

Free tier: 5MB/file (10MB for pdf-to-epub, 15MB for split), 3 operations/day, 15 req/min, output includes Epublys branding. Pro ($9/mo): 30MB per operation, unlimited daily operations, 60 req/min, no branding.

When a call is refused with daily_limited or a Pro-only error, call the upgrade_to_pro tool — it returns a checkout link to hand the user. Details: 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_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesBase64-encoded EPUB 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
includeImagesNoCopy referenced images into an images/ folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: artifact structure (ZIP, YAML frontmatter fields, index.md with linked TOC, images), free-tier output branding, size caps per operation, daily operation limits and req/min throttling, plus the error-recovery path. That is unusually rich behavioral disclosure for a mutation-free conversion tool.

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?

The purpose and return format are front-loaded in one dense sentence, followed by the operational constraints. The pricing block is long and partly marketing, but the limits and upgrade routing it contains do affect invocation decisions, so it mostly earns its place.

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

Completeness5/5

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

There is no output schema, and the description compensates fully by enumerating the return contents, the metadata/index files, and image handling. Size limits, rate limits, branding, and error handling are all covered, leaving nothing an agent needs to know before calling.

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 `file`, `name`, and `includeImages` are already fully documented in the schema, including the stem-based output naming and the images/ folder behavior. The description body adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

"Convert an EPUB ebook to Markdown" is a specific verb+resource, and the direction (EPUB → Markdown) makes it trivially distinguishable from the sibling markdown_to_epub. The second sentence then specifies exactly what artifact is produced (ZIP, one MD per chapter, index.md, images), so an agent knows the output shape before calling.

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

Usage Guidelines4/5

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

Usage context is clear (dropping converted output into an Obsidian vault or notes pipeline) and the description gives an explicit routing rule: on daily_limited or Pro-only errors, call upgrade_to_pro to fetch a checkout link. It does not explicitly contrast against read_epub_metadata, epub_to_pdf, or other siblings, so it falls short of a full when/when-not comparison.

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