Skip to main content
Glama
adamdavis99

ilovepdf-mcp

by adamdavis99

add-watermark

Add text or image watermarks to PDF files to protect ownership or brand content. Configure text, image, position, rotation, transparency, and page selection.

Instructions

Add a text or image watermark to a PDF document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPDF file path or URL to watermark
modeYesWatermark mode: text or image
textNoWatermark text (required for text mode)
imageNoWatermark image URL or path (required for image mode)
layerNoWatermark layer positionabove
pagesNoPage selection (e.g., "1-3,5,7-10" or "all")
mosaicNoEnable mosaic mode (repeat watermark across page)
fontSizeNoFont size in points
rotationNoRotation angle in degrees
fontColorNoFont color in hex format (e.g., #FF0000)#000000
fontStyleNoFont style
outputDirNoOutput directory path
fontFamilyNoFont familyArial
transparencyNoTransparency percentage (0-100)
outputFilenameNoCustom output filename
verticalPositionNoVertical positionbottom
horizontalPositionNoHorizontal positioncenter
Behavior2/5

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

With no annotations, the description must disclose side effects. It does not mention whether the original PDF is modified, whether a new file is created, how output location is determined, or any other behavioral traits. For a mutating tool, this is a substantial omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, which is efficient, but it is under-specified for a tool with 17 parameters. It could front-load key constraints such as mode-required fields and output behavior without excessive length.

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 high parameter count (17), no output schema, and no annotations, the description is incomplete. It only communicates the basic operation, leaving mode-specific requirements, page selection semantics, and file handling unspecified.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 17 parameters. The description adds no extra meaning beyond what the schema provides, only restating the text/image duality already present in the mode enum.

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 tool's action ('Add') and resource ('watermark to a PDF document'). It distinguishes from siblings by specifying both text and image watermark modes, which no other tool covers.

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 is provided on when to use this tool versus alternatives, when to choose text vs image mode, or any prerequisites or exclusions. The description simply states the action without contextual usage advice.

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/adamdavis99/ilovepdf-mcp'

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