Skip to main content
Glama
Sign In

OneSimpleAPI

by com.onesimpleapi
OverviewDiscussionsAdmin

POST /api/shortener/new

api_post_shortener_new
Destructive

Create short URLs with optional custom slugs, expiration dates, and tracking 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_shortener_new"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description goes beyond them by disclosing that outputs preserve HTTP status, headers and JSON/text/base64 bodies and that redirects are returned unfollowed. It also notes the tool consumes OneSimpleAPI credits and shares its permission/storage model, which is real operational context an agent would not get from the annotations.

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-loaded with the purpose in the first clause, then operational notes, with no filler sentences. Minor waste in restating that parameters can go in query or body (already evident from the schema) and a missing sentence break after 'tracking'.

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?

No output schema exists, and the description compensates by explaining how status codes, headers, bodies and redirects come back. For a non-idempotent creation tool with nested body/query/files/headers this is close to complete, though it says nothing about error behavior or whether re-posting the same URL creates duplicates.

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 documents url, custom_url, end_date, output and the boolean flags. The description only restates the field groups ('custom slugs, expiration dates, and tracking') without adding syntax, defaults, or interaction rules, so baseline 3 applies.

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?

Opens with a specific verb and resource: 'Create short URLs with optional custom slugs, expiration dates, and tracking.' That clearly separates it from the read/delete siblings (api_get_shortener, api_delete_shortener_delete), but it never names an alternative or states the boundary with api_post_unshorten, so differentiation is inferred rather than explicit.

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 invocation guidance ('Supply API parameters in query or body', 'This tool always uses POST; do not supply method') rather than selection guidance. It never says when to choose this over unshorten or the GET/PATCH/DELETE shortener siblings, so the when-to-use dimension is only implied.

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