Paperboy

Official

Overview Schema Source Related Servers Discussions Admin

crop_pages

DestructiveIdempotent

Crop PDF pages by top, right, bottom, and left margins in points, inches, or millimeters, or reset a page to show its full area again.

Instructions

Crop pages by margins [top, right, bottom, left], measured on the page as it is seen (rotation applied), in unit "pt" (points), "in" or "mm"; all pages or a page spec. reset=true instead shows the whole page again. Cropping only hides the margins: the content stays in the file (use sanitize or redaction to remove it). Needs the owner password if the PDF forbids changes. Signed PDFs are refused.

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>"
    },
    "name": "crop_pages"
  }
}

Input Schema

Name	Required	Default
`unit`	No	pt
`pages`	No
`reset`	No
`margins`	No
`password`	No
`overwrite`	No
`input_path`	Yes
`output_path`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: cropping hides margins but leaves content in the file, requires the owner password if the PDF forbids changes, refuses signed PDFs, and supports reset. It also explains the 'ask' password flow so the agent knows the password need not pass through chat. This is strong behavioral disclosure for a mutating PDF 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?

Front-loads the core action and margin/unit semantics, then adds important caveats about hiding versus removing content and password behavior. The password note is useful but slightly broadened into general guidance, keeping it just short of maximally tight.

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?

Given the 8-parameter schema and existing output schema, the definition covers the operation, units, page targeting, reset behavior, password handling, and refusal cases well enough for an agent to call it correctly. Remaining gaps around overwrite and output_path are secondary because the output schema and defaults elsewhere carry those concerns.

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

Parameters4/5

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

Despite 0% schema description coverage, the description explains several non-obvious parameters: margins are ordered [top, right, bottom, left], unit is pt/in/mm, pages can be all or a page spec, reset restores the whole page, and password may be 'ask'. Output_path and overwrite remain unexplained, so coverage is strong but not complete.

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 and resource plus the exact available scope: crop pages by margins, with reset restoring the whole page. It also distinguishes the operation conceptually from sanitize/redaction by explaining that cropping only hides content rather than removing it.

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?

Makes the use case clear and names sanitize or redaction as the alternative when actual removal is needed, and explains reset for undoing the crop visually. It does not explicitly compare with sibling tools such as resize_pages or rotate_pages, but the main when-to-use and alternative guidance is present.

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