PDFops

Remove PDF restrictions

pdf_unlock

Idempotent

Save a PDF without encryption so print/copy/modify restrictions are gone. Works for owner-locked files (empty user password) with no password, and for user-password files when you pass the password. It does NOT crack unknown passwords: a wrong or missing user password fails with encrypted_pdf. A PDF that was not encrypted is returned re-saved, with note "not-encrypted". Returns the result inline as an application/pdf resource; the source is never modified.

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

Input Schema

Name	Required	Description	Default
`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
`note`	No	Present as "not-encrypted" when the input had no encryption
`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.9/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the failure code (encrypted_pdf), the non-encrypted passthrough behavior with its "not-encrypted" note, the inline application/pdf return shape, and the guarantee that the source is never modified. The 'source never modified' guarantee is consistent with destructiveHint=false and the lack of readOnly is explained by the re-save/return behavior.

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 tight sentences, front-loaded with the outcome, then the supported cases, then the failure mode, then the return/immutability note. No redundant or decorative wording.

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?

Even though an output schema exists, the description covers the return modality, failure semantics, and non-destructive guarantee — everything an agent needs for a two-parameter file-transformation tool. Nothing material is left unspecified.

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?

Schema coverage is already 100%, so the schema carries the formal definitions; the description still adds operational meaning by tying the password parameter to the specific file classes that require it and reinforcing that path input must be a URL or data URI. The added value is modest but real rather than a verbatim restatement.

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 — save a PDF without encryption so print/copy/modify restrictions are removed — which is unmistakably distinct from siblings like pdf_protect. An agent can tell exactly what transformation happens to the file.

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?

Explicitly enumerates the two supported cases (owner-locked files with an empty user password need no password; user-password files require the password) and names the exclusion: it does NOT crack unknown passwords and fails with encrypted_pdf. This is a clear when/when-not statement with no inference required.

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?