Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

pdf_add_password

Add password protection to a PDF file to secure it with owner and user passwords, restricting access and setting permissions for printing, editing, and copying.

Instructions

Add password protection to a PDF file.
Ref: https://developer.pdf.co/api-reference/pdf-password/add.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to the source PDF file. Supports publicly accessible links including Google Drive, Dropbox, PDF.co Built-In Files Storage. Use 'upload_file' tool to upload local files.
owner_passwordYesThe main owner password that is used for document encryption and for setting/removing restrictions.
user_passwordNoThe optional user password will be asked for viewing and printing document.
encryption_algorithmNoEncryption algorithm. Valid values: RC4_40bit, RC4_128bit, AES_128bit, AES_256bit. AES_128bit or higher is recommended.AES_256bit
allow_accessibility_supportNoAllow or prohibit content extraction for accessibility needs.
allow_assembly_documentNoAllow or prohibit assembling the document.
allow_print_documentNoAllow or prohibit printing PDF document.
allow_fill_formsNoAllow or prohibit the filling of interactive form fields (including signature fields) in the PDF documents.
allow_modify_documentNoAllow or prohibit modification of PDF document.
allow_content_extractionNoAllow or prohibit copying content from PDF document.
allow_modify_annotationsNoAllow or prohibit interacting with text annotations and forms in PDF document.
print_qualityNoAllowed printing quality. Valid values: HighResolution, LowResolution.
httpusernameNoHTTP auth user name if required to access source url. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
passwordNoPassword of the PDF file if it's already password-protected. (Optional)
nameNoFile name for the generated output. (Optional)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)

Implementation Reference

  • The service-layer helper function add_pdf_password that executes the actual API call. It sends a request to the 'pdf/security/add' endpoint, passing additional keyword arguments as the custom payload (ownerPassword, EncryptionAlgorithm, permission flags, etc.).
    async def add_pdf_password(
        params: ConversionParams, api_key: str | None = None, **kwargs
    ) -> BaseResponse:
        return await request(
            "pdf/security/add", params, custom_payload=kwargs, api_key=api_key
        )
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states the basic action and does not disclose behavioral traits such as file modification, return values, permission requirements, or error scenarios.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with an external reference, making it concise but lacking structure. It is not front-loaded with critical information, and the brevity sacrifices completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (17 parameters, no annotations, no output schema), the description is severely incomplete. It does not explain return values, relationships between parameters, or any behavioral context, relying on an external link not part of the description.

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?

The schema has 100% description coverage for all 17 parameters, each with detailed descriptions. The tool description adds no additional meaning beyond what the schema already provides, meriting a baseline score of 3.

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 states 'Add password protection to a PDF file,' which clearly indicates the tool's purpose. However, it does not explicitly differentiate from sibling tools like pdf_remove_password, but the name itself provides sufficient differentiation.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for adding password protection, but lacks context on prerequisites or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pdfdotco/pdfco-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server