Skip to main content
Glama

TemPolor MCP Server by useapi.net (third-party)

Delete a track

tempolor_delete_music
DestructiveIdempotent

Delete one song or instrumental from its TemPolor account by job_id; the account comes from the job_id. To only stop this API tracking a running job use tempolor_stop_tracking. Answers result: true; a track TemPolor no longer has answers 404. Cannot be undone. DELETE /music/{job_id}.

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": {
      "job_id": "<job_id>"
    },
    "name": "tempolor_delete_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id of the track to delete, e.g. user:12345-tempolor:<user_id>-job:<itemId> (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is covered structurally; the description still adds real context beyond them: irreversibility ("Cannot be undone"), the success payload (result: true), and the 404 behavior for already-absent tracks. It does not mention auth/permission requirements, which is the main remaining gap.

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

Conciseness5/5

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

A single dense sentence that is front-loaded with the action and scoping rule, followed by the alternative tool, the return contract, and the endpoint. Every clause carries information; nothing is padding despite the semicolon-chained style.

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 one-parameter destructive tool with no output schema, the description covers the action, its scope, irreversibility, and the success/404 responses. Only the permission or account-authorization requirements are left implicit.

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?

With one parameter at 100% schema coverage, the schema already documents job_id and its format. The description reinforces the key insight that the job_id names the account, but that fact is also present in the schema, so it adds only marginal meaning beyond structured data.

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

Purpose5/5

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

States a specific verb and resource ("Delete one song or instrumental from its TemPolor account by job_id") plus the key that identifies it, and explicitly distinguishes itself from tempolor_stop_tracking. An agent can tell this apart from the midi/voice delete siblings without opening schemas.

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

Usage Guidelines4/5

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

Explicitly routes the agent away from this tool when the goal is only to stop tracking a running job ("use tempolor_stop_tracking"), and notes the 404 case when the track is already gone. It does not discuss whether deleting needs to follow a get_music check or list step, so it falls just short of full alternatives coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources