FreeDailyPro Tools

pptx_redact

Read-onlyIdempotent

Black out sensitive text in a PowerPoint (.pptx) from freedailypro and get the redacted .pptx (base64). Matches are replaced by block characters in the file's own text (not covered), on slides, notes, the master and layouts, charts, SmartArt, comments, alt text and link targets. presets: email, phone, ssn, card, url, ip, money, date; plus terms (exact words), regexes, imageSlides ('all' or slide numbers: pictures replaced by a black stand-in) and imageByAlt. stripNotes, stripComments and stripMetadata remove those entirely. The result is read again and any remaining match is reported (remaining, remainingWhere). Text inside pictures, video and audio cannot be found; warnings say what could not be checked. A deck with no match is returned unchanged with changed false.

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_redact"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Search speaker notes. Default true.
`terms`	No	Exact words or phrases
`presets`	No	Kinds of text to remove
`regexes`	No	Regular expressions (JavaScript syntax)
`template`	No	Search the master and layouts. Default true.
`matchCase`	No	Default false
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.
`imageByAlt`	No	Black out pictures whose name or alt text matches the terms or patterns
`stripNotes`	No	Remove all speaker notes
`imageSlides`	No	Black out the pictures on these slides, or all
`stripComments`	No	Remove all comments
`stripMetadata`	No	Remove author and file details
`dropChartWorkbooks`	No	Remove a chart's embedded workbook when it still holds a match. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotent/destructive=false, so the bar is lower, yet the description adds substantial behavior: matches are replaced in the file's own text, a verification pass reports 'remaining'/'remainingWhere', unsearchable content (pictures, video, audio) produces warnings, and an unmatched deck comes back unchanged with 'changed false'. That is exactly the operational context an agent needs before calling.

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?

The action and return value are front-loaded in the first sentence, followed by coverage scope, then parameter modes, then verification semantics. Dense but every clause carries distinct information; no filler or restatement of the title.

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 13-parameter, no-output-schema tool, the description covers return shape (base64 deck, remaining/remainingWhere, changed), limitations, and most parameter modes. The gaps are minor: dropChartWorkbooks and matchCase are never mentioned, and no note on size/slide limits beyond what the schema states.

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 baseline is 3; the description still adds meaning by explaining the coverage scope (slides, notes, master, layouts, charts, SmartArt, comments, alt text, link targets) and by clarifying imageSlides ('all' or slide numbers → black stand-in pictures) versus imageByAlt. It omits dropChartWorkbooks, matchCase, and the notes/template toggles, which keeps it from a 5.

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?

States a specific verb and resource — 'Black out sensitive text in a PowerPoint (.pptx)' — and names the return artifact ('get the redacted .pptx (base64)'). This clearly separates it from pptx_find_replace (which substitutes rather than blocks) and pdf_redact (different format).

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 implies usage by enumerating matching modes (presets, terms, regexes, imageSlides, imageByAlt) and states the no-match outcome, so an agent can infer when it applies. However, it never says when to choose this over sibling tools such as pptx_find_replace or pdf_redact, and gives no explicit exclusions or preconditions beyond the schema's file constraints.

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?