Skip to main content
Glama

pdf_extract_images

Extracts raster images from a PDF and saves them as PNG or JPEG files to a chosen directory, enabling offline image reuse from documents.

Instructions

Extract raster images from a PDF. [Input: PDF (.pdf) | Output: PNG/JPEG images]

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": {
      "input": "<input>",
      "output_dir": "<output_dir>"
    },
    "name": "pdf_extract_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
output_dirYesThe directory where images will be saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden and does not meet it. It never states whether it extracts only embedded/embedded raster objects versus rendering whole pages, whether existing files in output_dir are overwritten, what happens with image-free PDFs, or whether page images are one-per-page. The only behavioral fact disclosed is the output format (PNG/JPEG).

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?

Two short, front-loaded sentences with zero filler; the purpose comes first and the I/O summary follows. The bracketed I/O shorthand is slightly cryptic in style but costs almost no tokens, so there is little real waste.

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?

For a two-parameter extraction tool with no annotations and no output schema, the description is just barely adequate: it names the input and output types but omits the extraction semantics the agent needs. It says output is 'PNG/JPEG images' yet never clarifies whether they are written to disk (the schema implies output_dir) or returned.

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 both parameters (input path, output_dir) are already fully documented in the schema. The description adds nothing about path conventions, directory creation, or filename collisions, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Extract raster images from a PDF') and the I/O types in bracket notation, which lets an agent separate it from text/table/pattern extractors in the sibling list. It falls short of 5 because it never names an alternative or explicitly contrasts raster-image extraction with rendering pages 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing tells the agent when to pick this over pdf_extract_pages, pdf_extract_text, or pdf_images_to_pdf. The only selection signal is the implied 'raster images' vs other content types, which the agent must infer.

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