OneSimpleAPI

POST /api/image_manager

api_post_image_manager

Destructive

Transform one image with explicit quality, geometry, AI, composition and delivery controls; optionally derive responsive widths from one master. 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_image_manager"
  }
}

Input Schema

Name	Required	Description
`body`	No	API request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
`path`	No
`files`	No	Multipart 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.
`query`	No	URL query parameters. Sensitive API options must be in body as documented by the API.
`headers`	No	API request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
`content_type`	No	Defaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructive, open-world, non-idempotent behavior, so the bar is lower. The description still adds material context: shared permissions/credits/storage, preserved HTTP status and headers in output, redirects returned without following, each extra width costing one request, and paid-plan gating for AI upscaling.

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?

Front-loads the core purpose in the first clause, then layers transport and output facts. It is dense but every sentence contributes something; the only slight redundancy is restating that the tool always uses POST.

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 complex 6-parameter nested tool with no output schema, the description covers return shape (status, headers, JSON/text/base64 body), redirect handling, and the relationship between responsive widths and AI runs. Remaining gaps are minor and largely filled by the rich 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 description coverage is 83%, so the schema carries most parameter meaning and a 3 is the baseline. The description only adds that parameters may go in query or body and that options retain their original API meaning, without explaining individual options.

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: 'Transform one image' with quality, geometry, AI, composition and delivery controls, plus optional responsive widths. It clearly distinguishes an image-transformation operation from a metadata operation like api_post_image_info, though it never names a sibling to route against.

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?

Gives useful call-shape guidance: supply API parameters in query or body, always POST, do not supply method. But it offers no when-to-use or when-not-to-use guidance relative to alternatives such as api_post_image_info or api_get_image_recipes.

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

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