mcp-ebook-read

Overview Schema Source Related Servers Discussions Admin

pdf_list_images

Retrieve extracted images from a PDF document. Optionally filter by an outline node to get images from a specific section.

Instructions

List extracted PDF images, optionally scoped to an outline node. Use for general PDF visual evidence; use pdf_list_figures or pdf_list_tables for Docling-detected figure/table objects.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "pdf_list_images"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`doc_id`	Yes
`node_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Implies read-only operation but does not disclose requirements (e.g., document must be processed), or behavior like pagination. Adequate for a standard list tool but could be more explicit.

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 with no fluff. First sentence front-loads purpose, second provides sibling distinction. Every word earns its place.

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?

Given 3 params, no annotations, and existing output schema, the description covers basic purpose and sibling differentiation but lacks parameter details and behavioral context. Adequate but not comprehensive.

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

Parameters2/5

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

Schema coverage is 0%, and description only hints at node_id ('optionally scoped to an outline node'). No explanation for doc_id or limit parameters. Minimal added value 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?

Clearly states the action 'List' and resource 'extracted PDF images', with optional scoping to an outline node. Explicitly distinguishes from siblings pdf_list_figures and pdf_list_tables.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides direct guidance on when to use this tool ('general PDF visual evidence') and when to use alternatives (figures/tables tools). However, lacks prerequisites like document ingestion status.

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