Skip to main content
Glama
Sign In
PDF Reader MCP Server

PDF Reader MCP Server

by lihongwen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extract_pages

Extract selected pages from a PDF file into a new document. Specify page numbers or ranges to create a custom PDF with only the pages you need.

Instructions

Extract specific pages from PDF to a new file.

Args:
    file_path: Path to the source PDF file
    pages: Page range (e.g., "1,3,5-7" for pages 1, 3, and 5 to 7)
    output_file: Output filename (optional, auto-generated if not provided)
    output_dir: Output directory (defaults to source file directory)
    
Returns:
    JSON string with extraction results and output file information

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>"
    },
    "name": "extract_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
pagesYes
output_fileNo
output_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

The description explains the extraction process, return value (JSON string), and optional parameter defaults. No annotations are provided, so the description carries full burden; however, it does not mention permissions or whether the original file is modified.

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 concise and well-structured, using a list format for parameters and including return value info without any wasted words.

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

Completeness5/5

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

Given the tool's low complexity, the description covers purpose, parameters, and return value completely. The existence of an output schema is indicated by the return description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description fully compensates for the 0% schema coverage by explaining each parameter with examples, including the page range format and default behaviors for output_file and output_dir.

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 'Extract specific pages from PDF to a new file,' which is a specific verb and resource. It distinguishes from siblings like split_pdf (whole PDF splitting) and extract_page_text (text extraction).

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 description implies usage for page extraction but does not explicitly state when to use this tool versus alternatives like split_pdf or extract_page_text. No exclusion or comparative guidance is provided.

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