FreeDailyPro Tools

pptx_clean

Read-onlyIdempotent

Strip what you do not want to share from a PowerPoint (.pptx) from freedailypro, and get a clean .pptx back (base64): speaker notes, comments, hidden slides, author and company details with the revision list, and the stored preview picture. All of those are on by default; documentProperties (title, subject, keywords) and customProperties (labels and tags) are off by default. Slide content, layout and formatting are untouched, and parts only the removed slides used are dropped. Errors if every slide is hidden and hiddenSlides is on.

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

Input Schema

Name	Required	Description
`notes`	No	Remove speaker notes. Default true.
`comments`	No	Remove comments. Default true.
`thumbnail`	No	Remove the small preview picture stored in the file. Default true.
`authorInfo`	No	Remove author, last modified by, company, manager and the revision list. Default true.
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.
`hiddenSlides`	No	Delete slides that are hidden when presenting. Default true.
`customProperties`	No	Also remove custom document properties. Default false.
`documentProperties`	No	Also clear title, subject, keywords, description and category. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the structured fields and annotations, the description details crucial behaviors: what is intentionally preserved (slide content, layout, and formatting), how the removal works (dropped parts used), and which elements constitute specific categories (author and company details plus revision list). This adds significant operational context.

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?

The description is logically structured, starting with the main function and ending with preservation guarantees and error handling. It is highly efficient in that every sentence conveys a necessary piece of information, though it is detailed.

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?

Given the detailed input schema, the description provides all the necessary context for an agent to understand the input requirements (pptx base64 format) and the consequences of the operation (what will or will not be cleaned, and what the file will look like after processing).

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?

Since schema coverage is 100%, the description is not strictly necessary for defining the parameters. However, it adds value by mapping abstract boolean flags to real-world PPTX attributes (e.g., mapping the `authorInfo` flag to 'author, last modified by, company, manager and the revision list').

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 explicitly states its purpose is to strip unwanted elements and return a clean .pptx file in base64 format. It defines the output (clean PPTX) and the specific items it targets for removal (notes, comments, author details, etc.).

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

Usage Guidelines5/5

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

It provides crucial usage guidance by stating the default state for various flags (e.g., metadata removal is 'on' by default, document properties are 'off' by default). It also gives a clear failure condition: errors occur if every slide is hidden and hiddenSlides is set to true.

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?