Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

create_fillable_forms

Add fillable form fields like text boxes and checkboxes to a PDF document by specifying annotation properties including position, size, and type.

Instructions

Create new fillable form elements in a PDF document.

Example annotations format:
[
    {
        "text": "prefilled text",
        "x": 10,
        "y": 30,
        "size": 12,
        "pages": "0-",
        "type": "TextField",
        "id": "textfield1"
    },
    {
        "x": 100,
        "y": 150,
        "size": 12,
        "pages": "0-",
        "type": "Checkbox",
        "id": "checkbox1"
    }
]

Ref: https://developer.pdf.co/api-reference/pdf-add#create-fillable-pdf-forms.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.
annotationsYesList of form annotations to create. Each annotation can be a textfield or checkbox with properties like 'x', 'y', 'size', 'pages', 'type', and 'id'.
nameNoFile name for the generated output. (Optional)
httpusernameNoHTTP auth user name if required to access source url. (Optional)
httppasswordNoHTTP auth password if required to access source url. (Optional)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)

Implementation Reference

  • The fill_pdf_form_fields helper function that create_fillable_forms delegates to. It accepts optional fields and annotations, builds a custom_payload, and posts to the 'pdf/edit/add' endpoint.
    async def fill_pdf_form_fields(
        params: ConversionParams,
        fields: list | None = None,
        annotations: list | None = None,
        api_key: str | None = None,
    ) -> BaseResponse:
        custom_payload = {}
        if fields:
            custom_payload["fields"] = fields
        if annotations:
            custom_payload["annotations"] = annotations
        return await request(
            "pdf/edit/add", params, custom_payload=custom_payload, api_key=api_key
        )
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. It explains the annotations format but does not state whether the tool modifies the source PDF, returns a new file, or any error/rate-limit behaviors.

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?

Concise with a clear purpose statement, a useful example, and a reference link. The example is lengthy but appropriate for complex input.

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?

Adequately describes inputs with an example, but lacks output schema and error handling details. Missing information about return value or side effects, which is notable for a tool with 6 parameters and no output schema.

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 100%, providing baseline of 3. The description adds value by giving a detailed example of the 'annotations' parameter structure, which the schema only describes loosely. Other parameters are not further elaborated.

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?

The description clearly states 'Create new fillable form elements in a PDF document.' This is a specific verb+resource pair that distinguishes it from siblings like 'fill_forms' or 'pdf_add_annotations_images_fields'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or when not to use it.

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