PDFops

Delete pages from PDF

pdf_delete_pages

Idempotent

Remove the listed pages from a PDF and return the remaining pages in their original order. Use this to drop a cover, blank or sensitive pages; use pdf_extract_pages when it is easier to name the pages to keep. Returns the result inline as an application/pdf resource; the source is never modified. Deleting every page fails with no_pages_left.

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

Input Schema

Name	Required	Description
`pages`	Yes	1-based pages to REMOVE, e.g. "2,4-6,9-"
`password`	No	Password to open the input, only needed for a user-password PDF (owner-locked files with an empty user password open without it).
`pdf_path`	Yes	PDF source: an https:// URL or a data:application/pdf;base64,… URI (this hosted server cannot read local file paths).

Output Schema

Name	Required	Description	Default
`bytes`	Yes	Size of the produced PDF in bytes
`resource_uri`	No	pdfops:// uri of the inline application/pdf resource

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds context beyond the annotations: it clarifies that despite the "delete" name the source is never modified (reconciling with destructiveHint=false), states the return is an inline application/pdf resource, and discloses the no_pages_left failure when every page is deleted.

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?

Four short sentences, front-loaded with purpose, then usage/alternative, then return behavior, then the edge case. No filler and no repetition of the structured fields.

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?

For a 3-parameter tool with full schema coverage, an output schema, and annotations, the description covers purpose, alternative routing, non-destructiveness, and the single failure mode. An agent has everything needed to call it correctly.

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 the pages syntax, password rules, and pdf_path URL/data-URI constraints are already documented; the description only refers back to "the listed pages" without adding format or edge-case detail. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb+resource ("Remove the listed pages from a PDF") plus the output scope ("return the remaining pages in their original order"), which lets an agent distinguish it from pdf_extract_pages without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use cases (drop a cover, blank or sensitive pages) and explicitly names the alternative tool plus the condition that selects it: "use pdf_extract_pages when it is easier to name the pages to keep." Nothing is left to inference.

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

All PDFops tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?