FreeDailyPro PDF Tools

pdf_compress_aggressive

Read-onlyIdempotent

Shrink a PDF from freedailypro harder (the site's Aggressive mode): everything Balanced does, then pages become pictures in finer and finer steps (empty areas dropped, flat areas as plain fills, photos, text and small print at lower resolutions); a page is converted only when that is clearly smaller. Text on converted pages is no longer selectable and links and form fields on them are gone (textSelectable says which). Heavier than Balanced: it can take several seconds per page, and returns the best level finished so far (truncated: true) if the time budget runs out. Errors if the PDF is unreadable, password-protected, over 100 pages, or if nothing gets smaller.

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": "pdf_compress_aggressive"
  }
}

Input Schema

Name	Required	Description	Default
`fileBase64`	Yes	The PDF, base64 encoded (up to 20 MB, up to 100 pages)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With annotations only declaring this a safe, idempotent read, the description carries real load: it discloses the irreversible quality loss (text no longer selectable, links and form fields removed), the per-page time cost, and the truncated: true partial-result behavior on budget exhaustion. It also enumerates the failure modes (unreadable, password-protected, >100 pages, no size gain), which the structured data does not.

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 purpose is front-loaded and every sentence carries information, but the middle parenthetical enumeration of compression steps is dense and long-winded, making the definition heavier to parse than necessary for a one-parameter tool.

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?

There is no output schema, so the description usefully names the response fields it depends on (textSelectable, truncated) and lists error cases. It is nearly complete, though it never states the output encoding (presumably base64) or a rough expectation of achievable size reduction.

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 coverage is 100% and the single fileBase64 parameter is fully documented in the schema ('up to 20 MB, up to 100 pages'). The description only restates the page ceiling through error conditions and adds no new syntax or encoding detail, so the baseline 3 applies.

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 ('Shrink a PDF') and positions the operation relative to a named sibling ('everything Balanced does, then...'), including the degradation ladder (empty areas, flat fills, photos, text, small print). An agent can distinguish this from pdf_compress_balanced or pdf_compress_extreme without opening any schema.

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 gives a clear cost signal ('Heavier than Balanced', 'several seconds per page') and a timeout fallback, which implies when this is the right choice over the faster alternative. It does not explicitly say when to prefer pdf_compress_extreme or when to back off to Balanced, so the routing is implied rather than stated.

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

All FreeDailyPro PDF 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?