Skip to main content
Glama
Nizoka

pdfnative-mcp

Split PDF into ranges

split_pdf
Idempotent

Split a PDF into separate documents using page ranges. Each range becomes its own PDF file.

Instructions

Split one PDF into several documents — one per requested page range (pdfnative v1.4 page-tree API). Ranges are 0-based and inclusive; end defaults to start (a single page). Each output is a fresh, self-contained PDF (signatures/AcroForm dropped; URI links kept unless dropAnnotations=true). Encrypted sources are rejected (ENCRYPTED_SOURCE). In base64 mode every produced PDF is returned as its own embedded resource block; in file mode each is written to a 1-based indexed sibling of outputPath ('out.pdf' → 'out-1.pdf', 'out-2.pdf', …). Use extract_pages instead when you want a single PDF from an arbitrary page subset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangesYesPage ranges to extract, one output PDF per range. 0-based, inclusive; `end` defaults to `start` (a single page).
pdfBase64YesBase64-encoded source PDF. Must not be encrypted.
outputModeNobase64
outputPathNoBase output path (file mode). Each PDF is written to an indexed sibling: 'out.pdf' → 'out-1.pdf', 'out-2.pdf', …
dropAnnotationsNoWhen true, drop ALL annotations. Default keeps self-contained URI link annotations.
maxOutputSizeBytesNoMaximum size, in bytes, of each produced PDF. Defaults to 268435456 (256 MiB).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
countYes
partsYes
totalBytesYes
Behavior5/5

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

Description goes beyond annotations by detailing behavioral traits: signatures/AcroForm are dropped, URI links are kept unless dropAnnotations=true, encrypted sources rejected, and file mode naming convention. This provides transparency beyond the idempotentHint and destructiveHint annotations.

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 brief with three sentences, each providing essential information. It is front-loaded with the main purpose and includes necessary details without redundant information.

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?

Given the tool's complexity (6 parameters, annotations, output schema), the description covers key behaviors, edge cases (encrypted, file mode), and provides a pointer to an alternative tool. No gaps evident.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (83%), and description adds context: ranges are 0-based inclusive, end defaults to start, and file mode naming convention. Some parameters are not additionally detailed beyond schema, but the description adds value.

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?

The description clearly states the tool's purpose: 'Split one PDF into several documents — one per requested page range'. It specifies the resource (PDF) and the action. It also distinguishes from a sibling tool (extract_pages) by stating when to use that alternative.

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

Usage Guidelines5/5

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

Explicitly says when not to use: 'Use extract_pages instead when you want a single PDF from an arbitrary page subset'. Also mentions that encrypted sources are rejected (ENCRYPTED_SOURCE), providing clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nizoka/pdfnative-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server