FreeDailyPro Tools

pptx_find_replace

Read-onlyIdempotent

Find and replace text across every slide of a PowerPoint (.pptx) from freedailypro, and get the edited .pptx back (base64). Matches inside a paragraph are replaced even when PowerPoint split the words into several runs; the formatting of the first run is kept. Speaker notes are searched too (includeNotes, default true); the slide master and layouts only when includeTemplate is true. Errors with 422 when nothing matches, so a wrong spelling is noticed.

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>",
      "find": "<find>"
    },
    "name": "pptx_find_replace"
  }
}

Input Schema

Name	Required	Description
`find`	Yes	The text to look for
`replace`	No	The new text. Empty removes the match.
`matchCase`	No	Match upper and lower case exactly. Default false.
`wholeWord`	No	Match whole words only. 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.
`skipSlides`	No	Slide numbers to leave alone
`includeNotes`	No	Also change speaker notes. Default true.
`includeTemplate`	No	Also change the slide master and layouts (footers, company names in the design). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing implementation-critical traits: matches are found even when PowerPoint split a word into multiple runs, formatting of the first run is preserved, and a no-match condition raises 422 rather than a silent success. These are exactly the surprises an agent needs warned about 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?

Three tight sentences with the core promise front-loaded and no filler; the parenthetical defaults are brief restatements but read as scan anchors rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description covers the return type (base64 .pptx), error semantics (422 on no match), scope defaults, and run-splitting behavior. Combined with the schema's size/slide limits and file-type exclusions, an agent has everything needed to call this correctly.

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 what includeNotes and includeTemplate actually reach (speaker notes vs. master/layouts such as footers and design text). The note that the 422 fires when the find string misses adds per-parameter consequence that the schema cannot express.

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+resource (find and replace across every slide of a .pptx) plus the return value (edited .pptx as base64), which is enough to separate it from the generic find_and_replace and from pptx_replace_fonts. The scope 'every slide' is explicit and load-bearing.

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?

Clearly establishes the operating context: notes are in scope by default, master/layouts only with includeTemplate, and nothing-found yields a 422 so typos surface. It stops short of naming alternatives (find_and_replace for plain text, pptx_replace_fonts for typography), so the agent must infer when to prefer a sibling.

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?