Skip to main content
Glama
andr3medeiros

PDF Manipulation MCP Server

pdf_rotate_page

Rotate specific pages in PDF documents to correct orientation or adjust layout. Specify page number and rotation angle to modify PDF files.

Instructions

Rotate a page in a PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_pathYes
page_numberYes
rotationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'pdf_rotate_page' tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Validates input PDF and page, rotates the specified page using PyMuPDF's set_rotation(), generates output filename, and saves the modified PDF.
    @mcp.tool()
    async def pdf_rotate_page(
        pdf_path: str,
        page_number: int,
        rotation: int
    ) -> str:
        """Rotate a page in 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}"
        
        if rotation not in [90, 180, 270]:
            return f"Error: Invalid rotation angle. Must be 90, 180, or 270 degrees."
        
        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 and rotate it
            page = doc[page_number]
            page.set_rotation(rotation)
            
            # Generate output filename
            output_path = generate_output_filename(pdf_path)
            
            # Save the modified PDF
            doc.save(output_path)
            doc.close()
            
            return f"Successfully rotated page {page_number + 1} by {rotation} degrees. Output saved to: {output_path}"
            
        except Exception as e:
            return f"Error rotating page: {str(e)}"
  • Helper function used by pdf_rotate_page to validate the page number exists in the document.
    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)
  • Helper function used by pdf_rotate_page to validate the input is a valid 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_rotate_page to generate a timestamped output filename.
    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}")
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation (rotating pages) but doesn't disclose whether this modifies the original file or creates a copy, what permissions are needed, error conditions, or output format. This leaves significant gaps for a tool that alters PDF content.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 tool's complexity (mutating PDF pages), lack of annotations, and 0% schema coverage, the description is inadequate. While an output schema exists, the description doesn't address critical context like file handling, rotation units, or error scenarios, leaving the agent poorly informed.

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 parameters are undocumented in the schema. The description adds no semantic information about pdf_path (e.g., file path format), page_number (e.g., 1-indexed), or rotation (e.g., degrees, direction). It fails to compensate for the schema's lack of documentation.

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 action ('Rotate') and resource ('a page in a PDF'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like pdf_crop_page or pdf_auto_crop_page, which also modify page geometry, so it doesn't reach the highest score.

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. It doesn't mention prerequisites (e.g., needing an existing PDF), exclusions, or comparisons to similar tools like pdf_crop_page for different page adjustments.

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