APIVerve

PDF Merge

PDFMerge

Read-only

PDF Merge: PDF Merge combines 2 to 10 PDFs into one file, keeping their order, and returns a download link valid for 2 days. Upload the files or send their URLs. Paid plans add a breakdown of where each source document starts and ends in the merged file. (Cost: 10 credits)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "PDFMerge"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	No	A JSON array of 2 to 10 public PDF URLs, merged in order. Or upload the PDFs as multipart files instead

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world). The description does add useful operational detail beyond annotations: the link expires in 2 days, features are plan-gated, and the call costs 10 credits. See note below.

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?

One densely packed sentence plus two short ones, with the core action front-loaded. The redundant 'PDF Merge: PDF Merge' double naming at the start is the only wasted space.

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?

An output schema exists, yet the description still supplies the two things an output schema rarely conveys: link expiry (2 days) and per-call cost. Combined with input-mode guidance and limits, an agent has everything needed to call this correctly.

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?

With a single parameter and 100% schema description coverage, the schema already explains the 2-to-10 URL array, merge order, and the multipart-upload alternative. The description restates the same facts rather than adding syntax or format detail beyond it.

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 the specific verb and resource ('combines 2 to 10 PDFs into one file, keeping their order') plus the output shape (download link). This is clearly distinguishable from the many other PDF-related siblings (PDFtoImage, PDFPageNumbers, HTMLtoPDF), which do conversion or extraction rather than merging.

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?

Gives concrete context: batch size limits (2 to 10), two input modes ('Upload the files or send their URLs'), and when the extra breakdown feature applies (paid plans). It does not explicitly exclude alternatives, but no sibling competes directly on merging.

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

All APIVerve 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.