Skip to main content
Glama

pdf_delete_pages

Remove specific pages from a PDF by page number or range, then save the modified file to a chosen output path.

Instructions

Deletes specific pages. [Input: PDF (.pdf) | Output: PDF (.pdf)]

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>",
      "pages": "<pages>",
      "output": "<output>"
    },
    "name": "pdf_delete_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
pagesYesThe pages to delete, e.g., '1,3,5-7'.
outputYesFile path for the modified output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it contributes the I/O contract (PDF in, PDF out) which tells the agent the format is preserved. However, it does not state whether the input file is modified in place or whether the operation is reversible, nor does it describe error behavior for out-of-range or malformed page specifications. Those are significant gaps for a destructive operation.

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 sentences, front-loaded with the action, with no filler. The bracketed input/output notation is slightly template-like but conveys format information efficiently.

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 simple 3-parameter, fully required, fully documented tool with no output schema, the definition covers the basics. It stops short of the details that matter for a destructive file operation: whether the source file survives and how page numbering is interpreted.

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%, including the page-range syntax example ('1,3,5-7'), so the schema already does the semantic work. The description adds no additional meaning about indexing base, overlap handling, or output-path overwrite behavior, so the baseline of 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?

The description uses a specific verb-plus-resource ('Deletes specific pages') on a PDF, which is unambiguous about what the tool does. It does not explicitly contrast itself with sibling tools such as pdf_extract_pages, but the name and verb make the distinction obvious enough for selection.

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, no prerequisites, and no mention of alternatives such as pdf_extract_pages for the inverse operation. The only usage signal is the implicit 'delete pages from a PDF', which the name already conveys.

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