Skip to main content
Glama
NikhilBelwate

pdf-merger-mcp-server

Upload PDFs

pdf_merger_upload_pdfs

Upload PDF files for later merging. Start a new session or append files to an existing session before merging them.

Instructions

Upload one or more PDF files to the PDF Merger service for later merging.

Each file must be a valid PDF (≤100 MB). Up to 30 files can be uploaded per session. If session_id is provided, files are appended to that existing session; otherwise a new session is created.

Args:

  • file_paths (string[]): Absolute paths to PDF files on disk.

  • session_id (string, optional): UUID of existing session to append to.

Returns (JSON): { "session_id": "uuid", "files": [ { "id": "uuid", "name": "doc.pdf", "size": 102400, "sizeFormatted": "100.0 KB" } ] }

Examples:

  • Upload two files to a new session: file_paths=["/tmp/report.pdf", "/tmp/appendix.pdf"]

  • Append to existing session: file_paths=["/tmp/extra.pdf"], session_id="550e8400-..."

Error Handling:

  • File not found on disk → clear message with the missing path

  • Non-PDF file → 415 error from API

  • File >100 MB → 413 error from API

  • 30 files in session → 400 error from API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathsYesAbsolute file paths to PDF files on the local filesystem (e.g., ["/home/user/doc1.pdf", "/home/user/doc2.pdf"])
session_idNoOptional existing session ID to append files to. Omit to create a new session.
Behavior5/5

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

Beyond the annotations (which indicate non-read-only, non-idempotent, non-destructive), the description adds substantial behavioral context: file size limit, file count limit, error handling for missing files/non-PDF/oversized/exceeding limits, and session creation/appending behavior. This is far beyond what annotations provide.

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 well-structured with sections for description, args, return value, examples, and error handling. Every sentence adds necessary information without redundancy or fluff. It is appropriately sized for the tool's complexity.

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

Completeness4/5

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

The description is highly complete given the lack of an output schema: it specifies the return JSON structure, examples, and error cases. Minor gaps exist, such as not specifying behavior for an invalid session_id, but overall it is sufficient for an agent to use the tool correctly.

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?

The input schema already covers both parameters with descriptions (100% coverage), but the tool description adds value by including concrete examples, clarifying the session_id append-vs-new behavior, and explaining the expected file_paths format. This lifts it above the baseline of 3.

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 the tool uploads one or more PDF files to the PDF Merger service for later merging, using a specific verb and resource. It distinguishes itself from sibling tools (remove, merge, download URL) by focusing solely on the upload action.

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 provides clear context for when to use the tool (starting a session or appending to an existing one) and explains the session_id behavior. However, it does not explicitly contrast with alternative tools, so a 4 rather than 5 is appropriate.

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/NikhilBelwate/pdf-merger-mcp-server'

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