Skip to main content
Glama
Sign In
mcp-pdf-utils

mcp-pdf-utils

by zekovdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pdf_extract_pages

Extract specific pages from a PDF to create a new document. Specify start and end pages to isolate content sections or remove unwanted material.

Instructions

Extract a range of pages from a PDF into a new PDF 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": {
      "file": "<file>",
      "output": "<output>",
      "startPage": "<startPage>",
      "endPage": "<endPage>"
    },
    "name": "pdf_extract_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the source PDF file
outputYesOutput file path
startPageYesStart page (1-based)
endPageYesEnd page (1-based, inclusive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions creating a new PDF file but lacks critical behavioral details: whether the source file is modified, what happens if page ranges are invalid, if authentication or permissions are needed, or any rate limits. This is inadequate for a mutation tool.

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 a single, efficient sentence that front-loads the core action and outcome. Every word earns its place with no redundancy or unnecessary details, making it highly concise and well-structured.

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?

Given the tool's complexity (mutation with 4 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral traits, error conditions, or return values, leaving significant gaps for an AI agent to understand and invoke it correctly.

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 fully documents all 4 parameters. The description adds no additional parameter semantics beyond implying page extraction, which the schema already covers with startPage and endPage descriptions. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('extract a range of pages'), the resource ('from a PDF'), and the outcome ('into a new PDF file'). It distinguishes from siblings like pdf_extract_text (extracts text) and pdf_delete_pages (removes pages), making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like pdf_split (which might handle page extraction differently) or clarify scenarios where this is preferred over other PDF manipulation tools, leaving usage context implied.

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

Deploy Server

Other Tools