Skip to main content
Glama

Compress PDF

compress_pdf
Idempotent

Shrink your PDFs to send them by email or upload them to a form, at the quality you choose. Returns a link to download the result (kept about an hour). Credits on paid plans: 10 per file.

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": {
      "files": "<files>"
    },
    "name": "compress_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
levelNoCompression Values: 'baja' = Low (better quality); 'recomendada' = Recommended; 'extrema' = Extreme (smallest)recomendada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotency, open-world access, and non-destructiveness, so the bar is lower; the description still adds real value by disclosing that the result is a download link retained for roughly an hour and that paid plans charge 10 credits per file. It does not explain whether compression is synchronous or requires job_status polling, which is the one notable behavioral gap.

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?

Two sentences, front-loaded with the purpose and followed by the practical facts an agent needs (return artifact, lifetime, cost). Every clause carries information and nothing is repeated from the schema.

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 simple two-parameter tool with full schema coverage and no output schema, this covers the essentials: what it produces, how long the link lives, and the credit cost. It could be slightly more complete by clarifying sync vs. async behavior and whether the source file is left untouched.

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%, and the enum values for 'level' are already fully explained in the schema, so the description's phrase 'at the quality you choose' adds nothing new. The 'files' parameter's URL-vs-base64 dual input is likewise left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Shrink your PDFs') plus the intended outcome, which cleanly separates it from the other PDF siblings like merge_pdf, split_pdf, or jpg_to_pdf. It stops short of naming any sibling for contrast, but the operation is unambiguous on its own.

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 email/form framing implies when to reach for this tool, so usage is inferable rather than stated. There is no explicit when-not guidance, no mention of alternatives (e.g. when to use pdf_to_pdfa instead), and no prerequisites such as whether the file must already be uploaded.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources