Paperboy

Official

Overview Schema Source Related Servers Discussions Admin

delete_pages

DestructiveIdempotent

Remove specified pages from a PDF using page numbers or ranges, and supply the owner password if the document forbids assembly.

Instructions

Delete pages, e.g. pages="2,5-7". Needs the owner password if the PDF forbids document assembly.

Any password argument can be "ask": the user then types it on a local page, so it never passes through the chat.

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_path": "<input_path>",
      "pages": "<pages>"
    },
    "name": "delete_pages"
  }
}

Input Schema

Name	Required	Description	Default
`pages`	Yes
`password`	No
`overwrite`	No
`input_path`	Yes
`output_path`	No

Output Schema

Name	Required	Description	Default
`pages`	Yes
`output`	Yes
`deleted`	Yes
`password_protected`	Yes
`user_password_changed`	Yes
`permissions_restricted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Nov 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deleted": {
+      "items": {
+        "type": "integer"
+      },
+      "title": "Deleted",
+      "type": "array"
+    },
+    "output": {
+      "title": "Output",
+      "type": "string"
+    },
+    "pages": {
+      "title": "Pages",
+      "type": "integer"
+    },
+    "password_protected": {
+      "title": "Password Protected",
+      "type": "boolean"
+    },
+    "permissions_restricted": {
+      "title": "Permissions Restricted",
+      "type": "boolean"
+    },
+    "user_password_changed": {
+      "title": "User Password Changed",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "password_protected",
+    "permissions_restricted",
+    "user_password_changed",
+    "output",
+    "pages",
+    "deleted"
+  ],
+  "title": "DeleteResult",
+  "type": "object"
+}

First observedv0.1.0Oct 21, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is covered; the description adds genuine context beyond that, namely the permission dependency on document assembly and the "ask" password mechanism that keeps secrets out of the chat. It does not disclose whether the source file is modified or a new file is written, which matters for a destructive tool.

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 tight paragraphs: the primary operation and its selector syntax come first, the password caveat second. Nothing is redundant, though the generic password paragraph is only loosely tied to this specific tool.

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?

An output schema exists, so return values need not be explained. For a destructive page-removal tool, however, the description omits the critical question of whether overwrite/output_path cause the original PDF to be modified, which an agent needs before invoking it.

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 description coverage is 0% across 5 parameters, so the description carries the full burden. It explains the `pages` range syntax by example and the `password` value including the special "ask" token, but leaves `input_path`, `output_path` and `overwrite` entirely undocumented, so three of five parameters remain undefined.

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 ("Delete pages") and immediately grounds it with a concrete selector example ("pages="2,5-7""). It does not explicitly name a sibling to contrast with (e.g. crop_pages or extract_pages), but the operation is unambiguous against the listed page-manipulation tools.

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?

Provides a conditional prerequisite: an owner password is needed when the PDF forbids document assembly, which tells the agent when the call may fail. However, it never says when to delete pages versus alternatives like crop_pages or extract_pages, and gives no guidance on choosing between in-place and copy output.

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