FreeDailyPro Tools

pptx_watermark

Read-onlyIdempotent

Stamp a text watermark (such as DRAFT or CONFIDENTIAL) or a picture on the slides of a PowerPoint (.pptx) from freedailypro, or remove the watermarks this tool made, and get the new .pptx (base64). Give text, or pictureBase64 (PNG or JPEG) for a picture. It sits behind the slide content by default.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileBase64": "<fileBase64>"
    },
    "name": "pptx_watermark"
  }
}

Input Schema

Name	Required	Description
`bold`	No	Default true
`font`	No	Default Arial
`mode`	No	Default add
`size`	No	Points, or auto to fit the slide. Default auto.
`text`	No	The watermark words, for example DRAFT
`color`	No	Text colour, hex. Default 808080.
`layer`	No	Default behind
`place`	No	Default center
`slides`	No	Slides to mark. Default all.
`opacity`	No	Percent opaque. Default 30.
`rotation`	No	Degrees; negative rises to the right. Default -45 for text.
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.
`widthPercent`	No	Picture width as a percent of the slide. Default 50.
`pictureBase64`	No	A PNG or JPEG, base64, instead of text

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent, and the description adds real context beyond them: the output is a new .pptx returned as base64, the watermark is placed behind slide content by default, and removal only applies to marks this tool made. Size and slide-count limits are left to the schema rather than restated.

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?

Three sentences, front-loaded with the core action and return value, with the parameter choice and default layer following in priority order. Only minor waste in the vendor phrase 'from freedailypro'.

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?

For a 14-parameter, no-output-schema tool, the description covers what the operation produces (a new base64 .pptx) and the main behavioral default. It does not summarize the file-size/slide-count constraints or the add-vs-remove mode interplay, though those are documented in the schema.

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 100%, so the baseline is 3; the description still adds value by explaining the either/or relationship between 'text' and 'pictureBase64' and by confirming the default 'behind' layer behavior, which an agent might otherwise have to infer from the 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 names a specific verb and resource — stamping a text or picture watermark onto .pptx slides — and also covers the inverse operation (removing watermarks this tool created). The explicit '.pptx' format plus the stated base64 return value make it distinguishable from format siblings like pdf_watermark.

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

Usage Guidelines4/5

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

It tells the agent how to pick the two operating paths: give 'text' for a wordmark, or 'pictureBase64' (PNG or JPEG) for an image, and it scopes removal to watermarks this tool made. It stops short of naming alternatives (e.g., use pdf_watermark for PDFs) or stating prerequisites explicitly.

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

All FreeDailyPro Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?