OneSimpleAPI

PATCH /api/shortener

api_patch_shortener

Destructive

Existing api/shortener API operation. 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 PATCH. 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_patch_shortener"
  }
}

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.
`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.

First observedNov 5, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description usefully adds that output preserves HTTP status, headers and JSON/text/base64 bodies, that redirects are returned unfollowed, and that calls consume the same permissions, credits and storage as the underlying OneSimpleAPI. That redirect-handling and credit-cost detail is genuine context an agent cannot infer from the annotations, though no rollback or confirmation guidance accompanies the destructive flag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence 'Existing api/shortener API operation' largely restates the name and title and could be replaced by a functional statement. The remaining sentences about parameter placement, the method default, and response preservation are dense and carry real information, so the text is front-loaded but not wasteful throughout.

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 seven-parameter, nested-object HTTP passthrough with no output schema, the description covers what is needed to invoke it correctly: where parameters go, the fixed PATCH method, content-type behavior, and how responses and redirects come back. The main missing piece is an explicit statement of the mutation's effect (what 'destination_url' changes), which would round out a destructive, non-idempotent 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 71%, so the schema documents most parameters already, including the 'url' and 'destination_url' meanings and the files/headers shapes. The description adds only marginal meaning: that parameters may go in query or body, and that the method defaults to PATCH, without explaining the query-vs-body rule beyond the schema's note about sensitive options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies this as the 'Existing api/shortener API operation' issued as PATCH, which pairs a method with a resource, but it never states in plain terms what the operation accomplishes (updating the destination of an existing short URL). The functional meaning is only recoverable from the schema's 'destination_url' field description, so an agent must open the schema to distinguish this from api_post_shortener_new or api_delete_shortener_delete.

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?

The only operational instruction is 'Supply API parameters in query or body' and that 'method defaults to PATCH', which is transport mechanics rather than selection guidance. Nothing says when to choose this over api_post_shortener_new, api_get_shortener, or api_delete_shortener_delete, and no prerequisites or exclusions are given.

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?