OneSimpleAPI

DELETE /api/image-recipes/{name}

api_delete_image_recipes_name

Destructive

Delete one account-owned image recipe. Uses the OneSimpleAPI API (https://onesimpleapi.com/docs), with the same permissions, credits and storage. Supply API parameters in query or body. method defaults to DELETE. Outputs preserve HTTP status, headers and JSON/text/base64 body; redirects are returned without following them.

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": {
      "path": "<path>"
    },
    "name": "api_delete_image_recipes_name"
  }
}

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`	Yes
`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.
`method`	No
`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 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond that: output preserves HTTP status/headers/body, redirects are not followed, and permissions/credits/storage are shared with the underlying API. It still does not say whether deletion is reversible or what happens when the name does not exist.

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?

The purpose is front-loaded in the first sentence, followed by transport and output notes in compact form. Some boilerplate (the OneSimpleAPI URL, "same permissions, credits and storage") could be trimmed without losing meaning, but nothing is confusing or bloated.

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?

For a 7-parameter nested destructive endpoint with no output schema, the description does cover return handling (status, headers, body, redirects) reasonably well. It is incomplete on failure modes, idempotency expectations, and how to discover a valid recipe name, which matter for a delete operation.

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 71%, so the schema already documents most parameters, including body, query, files, headers and content_type. The description adds little parameter meaning beyond "method defaults to DELETE" (redundant with the single-value enum) and does not clarify that `name` must be an existing account-owned recipe identifier.

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?

"Delete one account-owned image recipe" states a specific verb (delete), resource (image recipe) and scope (one, account-owned). This clearly separates it from the sibling read/write endpoints like api_get_image_recipes and api_put_image_recipes without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives, no note that the recipe name can be obtained from api_get_image_recipes, and no warning about irreversibility or pre-delete verification. The only usage-adjacent sentence is "Supply API parameters in query or body," which is generic transport advice, not task guidance.

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?