Skip to main content
Glama

Apdf — PDF Tracking & Analytics

by io.apdf

Split PDF File

split-pdf-file

Split a PDF file into multiple files using a page-range expression (e.g. "1-3,4-6" for explicit ranges or "n3" for fixed chunks of 3 pages).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPublicly reachable URL of the PDF file to split.
asyncNoRun the action asynchronously and return a job id instead of the result. Poll "check-job-status" or set "webhook_url" to receive a callback.
pagesYesPage-range expression. Comma-separated ranges ("1-3,4-6"), "n[size]" for fixed chunks ("n1" = every page its own file), "r" (reverse), "z" (last page).
webhook_urlNoCallback URL invoked when an async job finishes. Only used when "async" is true.

TDQS

A3.8/5.0
Behavior3/5

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

The description adds the page-range expression syntax and examples, which is beyond annotations. However, it does not clarify whether the original file is preserved or if the result is multiple files or a zip. The synchronous versus async behavior is covered by parameters but not described.

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?

A single sentence with examples, no wasted words. Essential information is front-loaded.

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?

Given 4 parameters and no output schema, the description covers the core logic well. The only gap is not mentioning how the output is delivered (multiple files, download?). Overall adequate for a tool with good annotations.

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% with descriptions for all 4 parameters. The description adds clarifications for the 'pages' parameter with examples, but does not add meaning beyond what the schema provides for other parameters. 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?

The description clearly states the verb 'split' and the resource 'PDF file' into multiple files using a page-range expression. It distinguishes itself from sibling tools like delete-pdf-pages or extract-pdf-pages by focusing on splitting with ranges or fixed chunks.

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 implies usage for splitting PDFs but does not explicitly compare with alternatives like extract-pdf-pages or delete-pdf-pages. No guidance on when not to use or prerequisites.

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

All Apdf — PDF Tracking & Analytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a distinct operation (document management, PDF manipulation, automation, analytics, etc.) with clear boundaries, making it easy for an agent to select the correct one.

Naming Consistency5/5

All tool names follow a strict lowercase-with-hyphens pattern and use consistent verb-noun phrasing (e.g., 'create-document', 'list-documents', 'add-pdf-security'), ensuring predictability.

Tool Count2/5

At 45 tools, the server far exceeds the recommended 3-15 range for a well-scoped set. While the coverage is comprehensive, the high number may overwhelm agents and suggests insufficient consolidation.

Completeness5/5

The tool surface covers the full lifecycle of documents and PDFs—creation, retrieval, update, deletion, archiving, security, OCR, splitting, merging, automation, analytics, and more—with no obvious gaps.

Resources