Skip to main content
Glama
andr3medeiros

PDF Manipulation MCP Server

pdf_add_annotation

Add annotations like text, comments, or highlights to PDF documents by specifying page, position, and content for document collaboration and markup.

Instructions

Add an annotation to a PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_pathYes
page_numberYes
annotation_typeYes
xYes
yYes
widthYes
heightYes
contentYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler function for the 'pdf_add_annotation' tool, decorated with @mcp.tool() for automatic registration in FastMCP. It adds text, highlight, underline, or strikeout annotations to a PDF page at specified coordinates using PyMuPDF.
    @mcp.tool()
    async def pdf_add_annotation(
        pdf_path: str,
        page_number: int,
        annotation_type: str,
        x: float,
        y: float,
        width: float,
        height: float,
        content: str
    ) -> str:
        """Add an annotation to a PDF."""
        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]
            
            # Create rectangle for annotation
            rect = fitz.Rect(x, y, x + width, y + height)
            
            # Add annotation based on type
            if annotation_type == "text":
                annot = page.add_text_annot(rect, content)
            elif annotation_type == "highlight":
                annot = page.add_highlight_annot(rect)
                annot.set_info(content=content)
            elif annotation_type == "underline":
                annot = page.add_underline_annot(rect)
                annot.set_info(content=content)
            elif annotation_type == "strikeout":
                annot = page.add_strikeout_annot(rect)
                annot.set_info(content=content)
            else:
                doc.close()
                return f"Error: Invalid annotation type: {annotation_type}"
            
            # Update annotation appearance
            annot.update()
            
            # Generate output filename
            output_path = generate_output_filename(pdf_path)
            
            # Save the modified PDF
            doc.save(output_path)
            doc.close()
            
            return f"Successfully added {annotation_type} annotation to PDF. Output saved to: {output_path}"
            
        except Exception as e:
            return f"Error adding annotation to PDF: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool adds annotations but doesn't explain what happens (e.g., modifies the PDF file, requires write permissions, potential side effects like file size changes). This is inadequate for a mutation tool with zero annotation coverage.

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, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the complexity (8 required parameters, mutation operation, no annotations, but has output schema), the description is incomplete. It doesn't address parameter meanings, behavioral traits, or usage context, leaving significant gaps despite the output schema potentially covering return values.

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 by explaining parameters. It mentions 'annotation' but doesn't clarify what annotation_type, x, y, width, height, or content mean in context. The description adds minimal value beyond the schema's property names.

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

Purpose3/5

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

The description 'Add an annotation to a PDF' clearly states the action (add) and resource (annotation to PDF), but it's vague about what constitutes an annotation and doesn't differentiate from sibling tools like pdf_add_text or pdf_add_form_field. It's functional but lacks specificity.

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 like pdf_add_text or pdf_add_form_field. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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