PDF Tools

PDF Watermark Confidential

Generate dynamic confidential watermark with username and timestamp

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/pdf-watermark-confidential' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"sourceFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/pdf-watermark-confidential' \
  -F 'sourceFile=/Users/quyue/www/elysia-tools/public/samples/pdf/pdf-2026-02-19-source-4pages.pdf' \
  -F 'username=alice.wang' \
  -F 'policyText=INTERNAL USE ONLY' \
  -F 'timestampMode=iso' \
  -F 'opacity=0.22' \
  -F 'rotateDeg=-30' \
  -F 'fontSize=26' \
  -F 'colorHex=#b91c1c' \
  -F 'tile=true'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/pdf-watermark-confidential

Parameters

Name	Type	Required	Description
sourceFile	fileupload required	Yes	—
username	text	Yes	—
policyText	select	No	—
timestampMode	select	No	—
opacity	number	No	—
rotateDeg	number	No	—
fontSize	number	No	—
colorHex	color	No	—
tile	checkbox	No	—

File-type parameters must be uploaded first via POST /upload/pdf-watermark-confidential, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-pdf-watermark-confidential": {
      "name": "pdf-watermark-confidential",
      "description": "Generate dynamic confidential watermark with username and timestamp",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=pdf-watermark-confidential",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "pdf-watermark-confidential",
    "arguments": {
  "sourceFile": "/Users/quyue/www/elysia-tools/public/samples/pdf/pdf-2026-02-19-source-4pages.pdf",
  "username": "alice.wang",
  "policyText": "INTERNAL USE ONLY",
  "timestampMode": "iso",
  "opacity": 0.22,
  "rotateDeg": -30,
  "fontSize": 26,
  "colorHex": "#b91c1c",
  "tile": true
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]