Skip to main content
Glama

Organize the pages of a PDF

organize_pdf
Idempotent

Reorder the pages of a PDF by dragging them, rotate them or delete the ones you don't need, with every page shown as a thumbnail. 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": "organize_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).
pagesNoNew page order, comma-separated, pages numbered from 1, each with an optional ':angle' to rotate it (90, 180 or 270). Pages left out are removed and repeated ones are duplicated. Example: '3, 1:90, 2'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description's job is to add context, and it does: the return value is a download link that expires after about an hour, and paid plans cost 5 credits per file. That cost-and-lifetime detail is genuinely useful operational context an agent cannot get from structured fields. It does not state whether the original file is modified, though the download-link framing implies a new output file.

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?

Three compact sentences, front-loaded with the core action and followed by the return value and cost. Little waste, though the 'dragging'/'thumbnail' clause is not just extra words but actively misdescriptive of how this tool is invoked via a `pages` string.

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?

No output schema exists, but the description compensates by naming the return value (a downloadable link) and its expiry. Parameters are fully covered by the schema, and cost is disclosed. What's missing is whether the source document is left untouched, which matters given the tool can delete pages.

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 the schema already fully documents both `files` and `pages`, including the ':angle' rotation syntax and the duplicate/remove semantics. The description's mention of reorder/rotate/delete echoes the `pages` parameter but adds no format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives concrete verbs and a resource: reorder, rotate, or delete pages of a PDF. An agent immediately understands the transform. It does not differentiate from the overlapping siblings rotate_pdf and split_pdf, and the phrase 'by dragging them' / 'shown as a thumbnail' describes a UI experience rather than this parameter-driven API, which muddies rather than sharpens the purpose.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternatives. With rotate_pdf and split_pdf in the sibling set covering adjacent operations, an agent gets no help deciding which tool to pick when it only needs rotation or only needs extraction. The only contextual signal is a cost line, not selection guidance.

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