Skip to main content
Glama
EigenCharlie

pdf-toolkit-mcp

by EigenCharlie

add_watermark

Stamp a text or image watermark on every PDF page. Control placement, rotation, and opacity to protect or brand documents.

Instructions

Stamp a text or image watermark onto every page of a PDF. For mode="text", provide text. For mode="image", provide image_file (.jpg/.jpeg/.png). Tune placement, rotation, and opacity as needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes"text" stamps a text watermark; "image" stamps an image file onto each page.
textNoText to stamp. Required when mode="text".
layerNoWhether the watermark sits above the page content or behind it.above
opacityNoOpacity percentage (1-100). Default: 100.
rotationNoRotation in degrees (0-360). Default: 0.
image_fileNoPath to a .jpg/.jpeg/.png image to stamp. Required when mode="image".
input_fileYesPath to the PDF file to watermark.
output_pathNoOptional output path. If it ends with the expected extension, the file is written there. If it is a directory, the file is placed inside with a timestamped name. Defaults to the same directory as the first input.
vertical_positionNomiddle
horizontal_positionNocenter
Behavior4/5

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

With no annotations, the description adequately discloses functionality: stamps every page, explains modes, placement, rotation, opacity, and output path behavior. However, it could mention that the original file is not modified unless output_path is specified.

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?

Two sentences with no wasted words. The first sentence states the main purpose, the second gives critical mode-specific guidance. Ideal conciseness.

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

Completeness4/5

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

Given 10 parameters, 2 required, and no output schema, the description covers essential usage (mode, required fields, tuning). It lacks error handling or details on default output behavior, but is sufficient for a watermark tool.

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 80% so baseline is 3. The description adds value by explaining mode-dependent parameters (`text` for text mode, `image_file` for image mode) and summarizing tuning options, going beyond the schema.

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 verb 'Stamp' and the resource 'watermark onto every page of a PDF'. It distinguishes from sibling tools (e.g., add_page_numbers) by focusing on watermarking with modes for text and image.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for using the tool (watermarking PDFs) but does not explicitly state when to use vs alternatives or exclude sibling tools like add_page_numbers.

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/EigenCharlie/pdf-toolkit-mcp'

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