Skip to main content
Glama
Sign In
PDF MCP

PDF MCP

by gzigurella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extract_pages

Extract specific pages from a PDF file and save as a new PDF using page ranges or individual page selection.

Instructions

Extract specific pages from a PDF file and save as a new PDF. Supports page ranges and individual page selection.

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_path": "<file_path>",
      "pages": "<pages>",
      "output_path": "<output_path>"
    },
    "name": "extract_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYesPages to extract (e.g., '1-5', '3,7,9', '1,3-5')
file_pathYesPath to the source PDF file
output_pathYesPath where the extracted pages will be saved as a new PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Discloses basic behavior (saves new PDF) but lacks details on permissions, size limits, or error handling for out-of-range pages.

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?

Two concise sentences, no fluff, front-loaded purpose.

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?

Adequate for a simple tool with no output schema or annotations; could mention error behavior.

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 has 100% coverage with descriptions; description adds minimal value ('Supports page ranges...') beyond schema.

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?

Clear verb+resource: 'Extract specific pages from a PDF file and save as a new PDF.' Distinguishes from siblings like extract_text or pdf_to_images.

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?

Description implies usage context (extracting pages as PDF), but no explicit when-to-use or when-not-to-use vs alternatives.

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