mcp-pdf-utils

Overview Schema Source Related Servers Discussions Admin

pdf_reorder

Reorder PDF pages by specifying a custom sequence. Change page order to organize documents or create new arrangements from existing PDF files.

Instructions

Reorder pages of a PDF. Provide the desired page order.

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": {
      "file": "<file>",
      "output": "<output>",
      "order": "<order>"
    },
    "name": "pdf_reorder"
  }
}

Input Schema

Name	Required	Description
`file`	Yes	Path to the PDF file
`output`	Yes	Output file path
`order`	Yes	New page order as array of page numbers (1-based). E.g. [3,1,2] puts page 3 first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't mention whether the operation modifies the original file, creates a new file, requires specific permissions, or handles errors. 'Reorder pages' implies mutation but lacks transparency about the actual behavior.

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?

The description is perfectly concise with two clear sentences that directly state the tool's purpose and the key parameter requirement. Every word earns its place with no redundancy or unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens to the original file, what the output contains, or potential side effects. Given the complexity of file manipulation, more context is needed.

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 documents all parameters thoroughly. The description adds minimal value by hinting at the 'order' parameter's purpose but doesn't provide additional semantics beyond what's in the schema descriptions.

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 specific action ('reorder pages') and resource ('PDF'), distinguishing it from siblings like pdf_merge (combines files) or pdf_delete_pages (removes pages). It directly answers what the tool does with no ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like pdf_merge (for combining pages from multiple files) or pdf_extract_pages (for selecting specific pages). The description only states what it does, not when it's appropriate.

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

Deploy Server