Skip to main content
Glama

PDF Organize API - reorder, delete and reverse pages

pdf_organize
Read-onlyIdempotent

Give the new page order (3,1,2), delete pages (4-6) or reverse the whole document; pages you leave out of the order are dropped. 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-organize.

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": {
      "reverse": true,
      "fileName": "sample.pdf",
      "fileContent": "JVBERi0xLjMKJeLjz9MKMSAwIG9iago8PAovUHJvZHVjZXIgKHB5cGRmKQo+PgplbmRvYmoKMiAwIG9iago8PAovVHlwZSAvUGFnZXMKL0NvdW50IDEKL0tpZHMgWyA0IDAgUiBdCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9DYXRhbG9nCi9QYWdlcyAyIDAgUgo+PgplbmRvYmoKNCAwIG9iago8PAovVHlwZSAvUGFnZQovUmVzb3VyY2VzIDw8Cj4+Ci9NZWRpYUJveCBbIDAuMCAwLjAgNTk1IDg0MiBdCi9QYXJlbnQgMiAwIFIKPj4KZW5kb2JqCnhyZWYKMCA1CjAwMDAwMDAwMDAgNjU1MzUgZiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAwMDAwMDU0IDAwMDAwIG4gCjAwMDAwMDAxMTMgMDAwMDAgbiAKMDAwMDAwMDE2MiAwMDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDUKL1Jvb3QgMyAwIFIKL0luZm8gMSAwIFIKPj4Kc3RhcnR4cmVmCjI1NgolJUVPRgo="
    },
    "name": "pdf_organize"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOr several files: [{fileName, fileContent (base64)}]
orderNoNew order, e.g. 3,1,2 (pages left out are removed)
deleteNoPages to delete, e.g. 2, 5-7
reverseNoReverse the order (last page first)
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

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?

Goes well beyond the annotations by disclosing server-side execution, immediate deletion of uploaded files, no retention, a 25 calls/day per IP free tier, and a $0.005 x402 paywall with a URL. The one tension is that readOnlyHint=true sits alongside a note that input files are deleted after the call, but that describes ephemeral upload cleanup rather than mutation of a persistent resource, so it is not a true contradiction.

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 three operations and the page-dropping rule, then moves to privacy, then to pricing. It is dense but every clause carries information; the only mild clutter is stuffing rate-limit and payment details into the same block as functional semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description never says what comes back (base64 PDF, URL, or metadata), which is a real gap for an agent that must consume the result. It also does not clarify the zero-required-parameter situation or the interplay between the single-file and multi-file inputs.

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 100%, so the baseline is 3, and the description legitimately raises it by spelling out the order semantics ('3,1,2' plus 'pages you leave out of the order are dropped') and the delete range format ('4-6'). It does not cover how fileName/fileContent versus the files array are chosen when both exist.

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?

Names specific operations on a specific resource: reorder pages by giving a new order (3,1,2), delete a page range (4-6), or reverse the document. It also states the subtle rule that pages omitted from the order are dropped, which pins down the reorder semantic rather than leaving it ambiguous.

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 three supported modes are described, so an agent can infer when the tool applies, but there is no explicit when-not guidance or naming of alternatives such as pdf_rotate, pdf_split, or pdf_merge. The agent must infer that page manipulation belongs here and content-level edits elsewhere.

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