Skip to main content
Glama

Image Watermark API - text watermark on photos

image_watermark
Read-onlyIdempotent

Add a text watermark (e.g. © Your name) to one or many images: corner, centre or tiled, opacity, size, colour. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/image-watermark.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "© Example",
      "fileName": "sample.png",
      "fileContent": "iVBORw0KGgoAAAANSUhEUgAAAHgAAABQCAIAAABd+SbeAAAA6klEQVR4nO3cQQ2DABAAwdKgg1cFVQIykIOEyqiIisFDKdsQZv6XXDb3vmFa3jeOd//3AlchdEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6Mi4Z/jznH+0xmk8Xut3gy46InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ROiJ0ROiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNARoSNCR4SOCB0ZPIFtuOiI0BGhI0JHhI4IHRE6InRE6IjQEaEjQkeEjggdEToidEToiNCRDexBBl0OjJSaAAAAAElFTkSuQmCC"
    },
    "name": "image_watermark"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoText size, percent of the image width5
textNoWatermark text© Your name
colorNowhite or blackwhite
filesNoOr several files: [{fileName, fileContent (base64)}]
opacityNoOpacity percent50
fileNameNoFile name with extension, e.g. report.pdf
positionNobr, bl, tr, tl, c (centre) or tilebr
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint), the description discloses three things an agent cannot get from structured fields: processing happens server-side, source files are deleted immediately with nothing retained, and there is a hard 25 calls/day per-IP free cap plus $0.002/call paid path via x402. Cost and rate-limit disclosure is exactly the kind of operational context that prevents failed or unexpected-charge calls.

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

Conciseness4/5

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

Two sentences, front-loaded with the action and its capabilities, followed by operational facts. Dense but nearly every clause carries information; the pricing URL is the only element that feels tacked on rather than integrated.

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?

With 8 optional parameters, batch input via files, and no output schema, the description covers input shape ("one or many images"), privacy, and cost well. Its one real omission is the return value: it never says whether the result is a URL, base64 payload, or file reference, which matters precisely because no output schema exists to answer that.

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%, including enum values for position, opacity, size, and colour, so the schema already carries parameter meaning. The description restates the same option space at a high level ("corner, centre or tiled, opacity, size, colour") without adding format, default, or interaction details, so it sits at the baseline for a fully documented 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?

"Add a text watermark (e.g. © Your name) to one or many images" states a specific verb and resource, and immediately enumerates the configurable dimensions (corner, centre, tiled, opacity, size, colour). The word "images" cleanly separates it from the pdf_watermark sibling without needing to name it.

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?

Usage context is present but indirect: single vs. batch ("one or many images") and the free/paid tiers tell an agent what to expect operationally. There is no explicit when-to-use or when-not-to-use statement, and no routing to pdf_watermark or image_convert for adjacent needs, so the agent must infer the boundary from the resource noun alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources