Skip to main content
Glama
andr3medeiros

PDF Manipulation MCP Server

pdf_add_text

Insert custom text at precise coordinates on PDF pages to annotate documents, add labels, or include additional information.

Instructions

Add text to a PDF at a specified position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_pathYes
page_numberYes
textYes
xYes
yYes
font_sizeNo
colorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'pdf_add_text' tool. It adds text to a specified page and position in a PDF using PyMuPDF (fitz), generates a timestamped output file, and returns success/error message.
    @mcp.tool()
    async def pdf_add_text(
        pdf_path: str,
        page_number: int,
        text: str,
        x: float,
        y: float,
        font_size: int = 12,
        color: List[float] = None
    ) -> str:
        """Add text to a PDF at a specified position."""
        if color is None:
            color = [0, 0, 0]
        
        if not os.path.exists(pdf_path):
            return f"Error: PDF file not found: {pdf_path}"
        
        if not validate_pdf_file(pdf_path):
            return f"Error: Invalid PDF file: {pdf_path}"
        
        try:
            # Open PDF document
            doc = fitz.open(pdf_path)
            
            # Validate page number
            if not validate_page_number(doc, page_number):
                doc.close()
                return f"Error: Invalid page number {page_number}. Document has {len(doc)} pages."
            
            # Get the page
            page = doc[page_number]
            
            # Add text to the page
            page.insert_text(
                (x, y),
                text,
                fontsize=font_size,
                color=color
            )
            
            # Generate output filename
            output_path = generate_output_filename(pdf_path)
            
            # Save the modified PDF
            doc.save(output_path)
            doc.close()
            
            return f"Successfully added text to PDF. Output saved to: {output_path}"
            
        except Exception as e:
            return f"Error adding text to PDF: {str(e)}"
  • Utility function used by pdf_add_text to generate timestamped output filenames preventing overwrite of originals.
    def generate_output_filename(input_path: str, suffix: str = "modified") -> str:
        """Generate a new filename with timestamp to avoid overwriting originals."""
        path = Path(input_path)
        timestamp = datetime.now().strftime("%Y%m%d_%H%M%S")
        return str(path.parent / f"{path.stem}_{suffix}_{timestamp}{path.suffix}")
  • Helper function used by pdf_add_text to validate the input PDF file.
    def validate_pdf_file(pdf_path: str) -> bool:
        """Validate that the file is a valid PDF."""
        try:
            doc = fitz.open(pdf_path)
            doc.close()
            return True
        except Exception:
            return False
  • Helper function used by pdf_add_text to validate the page number.
    def validate_page_number(doc: fitz.Document, page_num: int) -> bool:
        """Validate that the page number exists in the document."""
        return 0 <= page_num < len(doc)
  • The server entry point that imports and runs the MCP server instance with all registered tools including pdf_add_text.
    def main():
        """Main function to run the MCP server."""
        mcp.run()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Add text') but doesn't disclose behavioral traits like whether this modifies the original PDF file, creates a new file, requires specific permissions, handles errors, or has rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste, making it easy to parse quickly.

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?

Given the tool's complexity (7 parameters, mutation operation) and the presence of an output schema (which reduces need to explain return values), the description is incomplete. It lacks parameter details, usage context, and behavioral transparency, but the output schema helps mitigate some gaps. It's minimally adequate but with clear deficiencies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'at a specified position,' which hints at x and y parameters, but doesn't explain any of the 7 parameters' meanings, formats, or constraints. The description adds minimal value beyond the schema, failing to address the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Add') and resource ('text to a PDF'), specifying the action and target. It distinguishes from some siblings like pdf_add_annotation or pdf_add_image by focusing on text, but doesn't explicitly differentiate from all similar tools like pdf_replace_text. The purpose is specific but could be more distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like pdf_replace_text and pdf_add_annotation available, there's no indication of when text addition is preferred over text replacement or annotation addition. No context or exclusions are mentioned.

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/andr3medeiros/pdf-manipulation-mcp-server'

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