pdf-merger-mcp-server

Get Download URL

pdf_merger_get_download_url

Read-onlyIdempotent

Create a one-time download link to retrieve a merged PDF. Use the token from the merge operation; the URL expires after one use.

Instructions

Build a one-time download URL for a merged PDF.

The token is returned by pdf_merger_merge. Each token can only be used once; after the first download the link expires and all associated cloud files are cleaned up.

Args:

token (string): One-time download token UUID from the merge response.

Returns (JSON): { "download_url": "https://your-api.example.com/download/" }

Notes:

Opening the URL in a browser triggers a file download of "merged.pdf".
After download, source blobs are automatically deleted from cloud storage.

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": {
      "token": "<token>"
    },
    "name": "pdf_merger_get_download_url"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	One-time download token returned by the merge operation. Each token can only be used once.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds critical behavioral context: tokens are one-time use, the link expires after first download, and associated cloud files are cleaned up. It also notes that opening the URL triggers a download of 'merged.pdf' and source blobs are deleted. This goes well beyond the annotations.

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?

The description is efficiently organized with a summary, args, returns, and notes. Every sentence adds value, and the most important information is front-loaded. No redundancy.

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?

For a simple single-parameter tool, the description fully covers preconditions, behavior, return format, and side effects. Even without an output schema, it outlines the return JSON. Complete and self-sufficient.

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% with a well-described token parameter. The description reinforces the source ('from the merge response') and one-time nature, adding context not present in the schema. Slight value beyond the schema.

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 opens with a specific verb+resource: 'Build a one-time download URL for a merged PDF.' This clearly distinguishes it from sibling tools (merge, upload, remove) and states exactly what the tool does.

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?

The description explicitly states the prerequisite: 'The token is returned by pdf_merger_merge.' This tells the agent when to use the tool, though it does not explain exclusions or when not to use it. The context is clear enough for correct deployment.

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

Deploy Server