Skip to main content
Glama

PDF Split API - extract or remove pages, one file per page

pdf_split
Read-onlyIdempotent

Split a PDF: keep pages (mode=pick, pages='1-3, 5'), remove pages (mode=remove) or one PDF per page (mode=each). Password-protected PDFs open with password. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/pdf-split.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "each",
      "fileName": "sample.pdf",
      "fileContent": "JVBERi0xLjMKJeLjz9MKMSAwIG9iago8PAovUHJvZHVjZXIgKHB5cGRmKQo+PgplbmRvYmoKMiAwIG9iago8PAovVHlwZSAvUGFnZXMKL0NvdW50IDEKL0tpZHMgWyA0IDAgUiBdCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9DYXRhbG9nCi9QYWdlcyAyIDAgUgo+PgplbmRvYmoKNCAwIG9iago8PAovVHlwZSAvUGFnZQovUmVzb3VyY2VzIDw8Cj4+Ci9NZWRpYUJveCBbIDAuMCAwLjAgNTk1IDg0MiBdCi9QYXJlbnQgMiAwIFIKPj4KZW5kb2JqCnhyZWYKMCA1CjAwMDAwMDAwMDAgNjU1MzUgZiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAwMDAwMDU0IDAwMDAwIG4gCjAwMDAwMDAxMTMgMDAwMDAgbiAKMDAwMDAwMDE2MiAwMDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDUKL1Jvb3QgMyAwIFIKL0luZm8gMSAwIFIKPj4Kc3RhcnR4cmVmCjI1NgolJUVPRgo="
    },
    "name": "pdf_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNopick, remove or eacheach
filesNoOr several files: [{fileName, fileContent (base64)}]
pagesNoPages, e.g. 1-3, 5, 8-
fileNameNoFile name with extension, e.g. report.pdf
passwordNoPDF password if it is protected
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing server-side execution, immediate file deletion with nothing stored, password handling for protected PDFs, a 25 calls/day IP limit, and a $0.005 paid path via x402. It does not describe the response shape (e.g. whether multiple files come back as base64 or links), which matters for a multi-output operation; the cited rates could also drift from the live service.

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?

Front-loads the core capability and mode list, then tacks operational facts onto the end with no filler sentences. It reads as one long run-on paragraph rather than separable capability/limits blocks, but every clause carries information.

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?

Covers the operation, mode semantics, privacy, cost and auth for a 6-parameter tool with no output schema. The one material omission is what the caller receives back — especially for mode=each where multiple files are produced — which the absence of an output schema leaves undocumented.

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% and the schema already documents mode, pages syntax, fileName, fileContent and password, so the description's restatement of pages and password adds little. It does tie mode values to concrete behaviors, which is mild added value over the enum list alone, but baseline 3 is right when the schema does the heavy lifting.

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+resource (split a PDF) and enumerates the three concrete outcomes — keep pages, remove pages, or one file per page — with a worked syntax example ('1-3, 5'). An agent knows exactly what the tool produces without opening the schema.

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?

The mode descriptions effectively serve as when-to-use guidance for each of the three behaviors, and the pages example shows how pick/remove arguments are formed. It stops short of contrasting with sibling tools such as pdf_merge or pdf_compress, so there is no explicit routing away from alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources