Skip to main content
Glama

Split PDF

split_pdf
Idempotent

Split a PDF into several: one page per file or the page ranges you choose. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per file.

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": {
      "files": "<files>"
    },
    "name": "split_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf), exactly 1. Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
rangesNoPage ranges. Page ranges, comma-separated: '1-3' are pages 1 to 3, '5' only page 5 and '8-' from page 8 to the end. Each range becomes its own PDF. Empty: one PDF per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint false, destructiveHint false, idempotentHint true, openWorldHint true). The description adds genuinely non-structured context: the return value is a download link, links expire after about an hour, and usage costs 5 credits per file on paid plans — cost and retention are exactly the kind of facts schema fields cannot carry.

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?

Three short sentences, front-loaded with the operation and its output shape, then retention, then cost. Every sentence carries distinct information with no padding.

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?

For a two-parameter tool with no output schema, the description covers the operation, result delivery, link lifetime, and pricing — enough to invoke correctly. Only minor gaps remain, such as failure behavior for malformed or oversized inputs, which the schema partially covers via the 20 MB note.

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 description coverage is 100%, so both `files` and `ranges` are fully documented upstream, and the baseline of 3 applies. The description restates the range-mode behavior in prose but adds no syntax or edge-case detail beyond what the schema already says.

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 ("Split a PDF into several") plus the exact output granularity (one page per file or chosen page ranges). That clearly separates it from merge_pdf, organize_pdf, and compress_pdf without needing to name them.

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?

The description defines the two split modes and notes that empty ranges produce one PDF per page, which implicitly tells an agent when this tool fits. It gives no explicit when-not guidance or pointer to alternatives like merge_pdf or organize_pdf for related tasks.

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