FreeDailyPro Tools

pptx_compress_size

Read-onlyIdempotent

Compress a PowerPoint (.pptx) from freedailypro to a size you need, such as under 10 MB for an email or an upload form. Runs from the sharpest picture setting to the coarsest and returns the sharpest result that fits targetSize, with targetMet: true. If it cannot fit, you get the smallest file it can make with targetMet: false and a note. A deck already at or under the target is returned unchanged. Pictures (JPEG, PNG, BMP) are re-saved smaller, unused layouts and the preview picture are removed, and the file is re-packed at maximum compression; text, charts, animations, audio and video are left exactly as they are, so the deck stays fully editable. Always returns the .pptx as base64 plus originalBytes, outputBytes, reductionPercent and the pictures changed, even when it could not get smaller (a note says so).

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>",
      "targetSize": "<targetSize>"
    },
    "name": "pptx_compress_size"
  }
}

Input Schema

Name	Required	Description
`maxDpi`	No	Never keep pictures sharper than this many dpi (48 to 300), on top of the level.
`fileBase64`	Yes	The presentation (.pptx), base64 encoded. Up to 50 MB and 500 slides. Old .ppt files and password-protected files are not supported.
`targetSize`	Yes	The size to reach: a number of bytes, or text such as 10MB or 800KB (at least 1 KB)
`removeNotes`	No	Also remove speaker notes first. Default false.
`removeThumbnail`	No	Remove the stored preview picture. Default true; send false to keep it.
`removeUnusedLayouts`	No	Remove slide layouts no slide uses, and the pictures only they carry. Default true; send false to keep them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / removeThumbnail / description

Previous value: -"Also remove the stored preview picture. Default false."New value: +"Remove the stored preview picture. Default true; send false to keep it."

changedInput schema / properties / removeUnusedLayouts / description

Previous value: -"Also remove slide layouts no slide uses, and the pictures only they carry. Default false."New value: +"Remove slide layouts no slide uses, and the pictures only they carry. Default true; send false to keep them."

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations: the sharpest-to-coarsest search order, targetMet true/false semantics, the no-op case for already-small decks, exactly what is altered (JPEG/PNG/BMP re-saved, unused layouts and preview picture dropped, re-packed at max compression) and what is preserved (text, charts, animations, audio, video). Annotations only supply the safety/idempotency profile, so this is meaningful extra 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?

Front-loaded with the core action and target use case, and nearly every clause carries contract information (targetMet, unchanged passthrough, what is and isn't modified). It is one dense, long paragraph whose run-on clauses (the return-value sentence in particular) cost some readability.

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?

There is no output schema, and the description compensates fully by enumerating the return payload (base64 .pptx plus originalBytes, outputBytes, reductionPercent, pictures changed, targetMet) even in the failure case. For a 6-parameter transformation tool that is complete enough to call correctly without further probing.

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%, so every parameter is already documented, including maxDpi's interaction with the level. The description explains the level-sweep mechanism that maxDpi qualifies and the default removals for thumbnail/layouts, but adds no new syntax or format detail for targetSize or fileBase64. Baseline 3 is appropriate.

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 ('Compress a PowerPoint (.pptx)') plus the distinguishing mechanism ('to a size you need', i.e. a target-size-driven sweep). That mechanism implicitly separates it from the fixed-level siblings (pptx_compress_default, pptx_compress_medium, pptx_compress_strong).

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?

Gives concrete motivating contexts ('under 10 MB for an email or an upload form') and the fallback contract when the target cannot be met. It does not explicitly name the alternative level-based compress tools or say when to prefer them over this one, which keeps it short of a 5.

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?