Skip to main content
Glama

Apdf — PDF Tracking & Analytics

by io.apdf
OverviewAdmin

Rotate PDF Pages

rotate-pdf-pages

Rotate one or more pages in a PDF by a multiple of 90 degrees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPublicly reachable URL of the PDF file to rotate pages in.
asyncNoRun the action asynchronously and return a job id instead of the result. Poll "check-job-status" or set "webhook_url" to receive a callback.
rotationsYesList of rotation operations. Each item: { "angle": "+90"|"-90"|"180"|..., "pages": "page-range" }.
webhook_urlNoCallback URL invoked when an async job finishes. Only used when "async" is true.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

Annotations declare destructiveHint: false, but the description does not clarify whether rotation modifies the file in place or creates a new version. It also fails to mention async behavior. The description adds minimal transparency beyond the annotation.

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?

The description is a single, precise sentence with no wasted words, front-loading the core purpose effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 4 parameters and no output schema, the description does not explain return values, async job mechanics, or any prerequisites like file size limits. It lacks completeness for a transformation tool.

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 describes all parameters. The description does not add additional meaning beyond what is in the schema, meeting the baseline.

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 clearly states the action (rotate), resource (PDF pages), and constraint (multiple of 90 degrees), distinguishing it from sibling tools like delete-pdf-pages or extract-pdf-pages.

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 description does not explicitly state when to use this tool versus alternatives. While the operation is straightforward, no guidance on context or exclusions is provided.

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

All Apdf — PDF Tracking & Analytics toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources