Skip to main content
Glama

Rotate PDF

rotate_pdf
Idempotent

Rotate the pages of your PDFs by 90, 180 or 270 degrees, all of them or only the ones you choose, and save them that way. 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": "rotate_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNoRotation Values: '90' = 90° clockwise; '180' = 180°; '270' = 90° counter-clockwise90
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).
rangesNoPages. Pages to rotate, as ranges ('1-3, 5, 8-'). Empty: all pages.

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 it is not read-only, is idempotent, and is non-destructive. The description adds genuinely useful context beyond that: the result is delivered as a download link that expires in about an hour, and paid plans are charged 10 credits per file. It does not mention permission or rate-limit behavior, but the key operational traits are disclosed.

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?

A single sentence front-loads the operation, its options, and its scope, then a second short sentence covers the return value and cost. No filler or redundancy.

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 correctly explains what comes back (a temporary download link). Cost and page-selection behavior are covered, and the remaining gaps (file size limits, input format details) are already handled by the fully described schema.

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%, so the schema already documents the angle enum, the file input forms, and the range syntax including the empty-means-all default. The description only echoes those facts in prose ('90, 180 or 270 degrees', 'all of them or only the ones you choose') without adding format or edge-case detail, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Rotate the pages of your PDFs') and scopes it precisely: angles of 90/180/270, all pages or a selected subset, saved in place with a downloadable result. That is enough to distinguish it from file-conversion siblings, though it never names a sibling or clarifies its boundary with organize_pdf.

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?

Usage is implied by the operation itself (fix page orientation, rotate selected pages) rather than stated. There is no explicit when-to-use guidance, no exclusions, and no pointer to an alternative such as organize_pdf for reordering rather than rotating.

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