Skip to main content
Glama
Sign In

OneSimpleAPI

by com.onesimpleapi
OverviewDiscussionsAdmin

POST /api/pdf

api_post_pdf
Destructive

Generate a PDF from any webpage or HTML content Uses the OneSimpleAPI API (https://onesimpleapi.com/docs), with the same permissions, credits and storage. Supply API parameters in query or body. This tool always uses POST; do not supply method. Outputs preserve HTTP status, headers and JSON/text/base64 body; redirects are returned without following them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "api_post_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoAPI request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
pathNo
filesNoMultipart uploads keyed by API field name (for example pdf). Supply file_name, base64 bytes and optional mime_type. Uploads use the existing API file validators.
queryNoURL query parameters. Sensitive API options must be in body as documented by the API.
headersNoAPI request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
content_typeNoDefaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real behavioral context: shared OneSimpleAPI permissions, credit consumption, storage side effects, HTTP status/header preservation, and that redirects are returned unfollowed rather than chased. What it does not explain is why destructiveHint=true applies to a PDF generation call, which is the most surprising annotation for an agent to reconcile.

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?

Four sentences, front-loaded with the capability before the transport rules, and no filler. The OneSimpleAPI sentence is slightly dense with parenthetical URL, but it earns its place by anchoring credits and permissions.

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

Completeness3/5

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

With no output schema, the description does the right thing by explaining that responses preserve status, headers and body types. However, for a tool with a deeply nested option surface and a destructive annotation, it leaves the source_group requirement and the destructive semantics unexplained, so an agent still has to open the schema to call it safely.

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 83%, so the schema already carries most parameter meaning, and the baseline is 3. The description adds the query-vs-body placement rule and the redirect/output nuance, but says nothing about the URL-or-HTML requirement or which of the dozens of nested options are commonly needed.

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?

"Generate a PDF from any webpage or HTML content" is a specific verb+resource pair, and it implicitly separates this tool from rendering siblings like api_post_screenshot or api_post_readability. It stops short of naming a sibling or stating the URL-vs-HTML exclusivity, which is left to the schema's source_group note.

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?

It gives concrete invocation guidance (supply parameters in query or body, always POST, never supply method), which prevents a common error. But there is no when-to-use or when-not-to-use versus the other document/render tools, and no statement about credits being consumed or when to prefer this over screenshot.

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

All OneSimpleAPI toolsInspect
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