Skip to main content
Glama

merge_pdfs

Merge multiple base64-encoded PDFs into a single PDF file. Provide an array of PDF strings; returns the combined document as a base64-encoded output.

Instructions

Merge multiple PDFs into a single PDF.

Args: pdfs_base64: List of base64-encoded PDF files to merge.

Returns: Base64-encoded merged PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdfs_base64Yes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool 'merge_pdfs' is registered via @mcp.tool() decorator. It accepts a list of base64-encoded PDFs, decodes them, calls the DocGen client's merge_pdfs, and returns the result as base64-encoded string.
    @mcp.tool()
    def merge_pdfs(pdfs_base64: list[str]) -> str:
        """Merge multiple PDFs into a single PDF.
    
        Args:
            pdfs_base64: List of base64-encoded PDF files to merge.
    
        Returns:
            Base64-encoded merged PDF.
        """
        dg = _get_client()
        files = [base64.b64decode(p) for p in pdfs_base64]
        merged = dg.merge_pdfs(files)
        return base64.b64encode(merged).decode()
  • The tool is registered with the FastMCP server using the @mcp.tool() decorator, making it available as an MCP tool named 'merge_pdfs'.
    @mcp.tool()
    def merge_pdfs(pdfs_base64: list[str]) -> str:
        """Merge multiple PDFs into a single PDF.
    
        Args:
            pdfs_base64: List of base64-encoded PDF files to merge.
    
        Returns:
            Base64-encoded merged PDF.
        """
        dg = _get_client()
        files = [base64.b64decode(p) for p in pdfs_base64]
        merged = dg.merge_pdfs(files)
        return base64.b64encode(merged).decode()
  • Sync DocGen client's merge_pdfs method that delegates to PdfToolsClient.merge().
    def merge_pdfs(self, files: list[FileInput]) -> bytes:
        """Merge multiple PDF files into one.
    
        Args:
            files: List of PDF files (paths, bytes, or base64).
    
        Returns:
            Merged PDF bytes.
        """
        return self._pdf_tools.merge(files)
  • Async DocGen client's merge_pdfs method that sends base64 PDFs to the /api/pdf-tools/merge/base64 endpoint.
    async def merge_pdfs(self, files: list[FileInput]) -> bytes:
        """Merge multiple PDFs asynchronously."""
        pdfs = [to_base64(f) for f in files]
        return await self._transport.request_bytes(
            "POST", "/api/pdf-tools/merge/base64",
            json={"pdfs": pdfs},
        )
  • PdfToolsClient.merge() - the low-level implementation that converts files to base64 and sends a POST request to /api/pdf-tools/merge/base64.
    def merge(self, files: list[FileInput]) -> bytes:
        """Merge multiple PDFs into one.
    
        Args:
            files: List of PDF files to merge (in order).
    
        Returns:
            Merged PDF bytes.
        """
        pdfs = [to_base64(f) for f in files]
        return self._transport.request_bytes(
            "POST", "/api/pdf-tools/merge/base64",
            json={"pdfs": pdfs},
        )
Behavior2/5

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

No annotations are provided, and the description only states the basic operation. It does not disclose behavioral traits such as order preservation, error handling, or file size limits, which are important for a merge tool.

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 concise with two sentences in docstring format, no wasted words, and clearly structured with Args and Returns sections.

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?

The description is adequate for a simple merge tool, but lacks behavioral details like error handling or ordering. Since an output schema exists, return value explanation is not needed.

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 0%, but the description adds meaning by specifying that 'pdfs_base64' is a list of base64-encoded PDF files to merge, compensating for the schema's lack of detail.

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 action (merge), the resource (multiple PDFs), and the output (single PDF), distinguishing it from sibling tools like convert_to_pdfa or generate_pdf_from_html.

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. Siblings include many PDF operations, but no explicit when-to-use or when-not-to-use context is provided.

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/dokmatiq/docgen-sdks'

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