Skip to main content
Glama

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

Stop tracking a job

tempolor_stop_tracking
DestructiveIdempotent

Stop this API tracking a running job (a job_id from tempolor_list_running_jobs) and free its maxJobs slot on the account. It does not cancel the job at TemPolor: the track is still made and tempolor_get_music still reads it, but its replyUrl callbacks stop. 404 when the job_id is not being tracked. Cannot be undone. DELETE /scheduler/{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_stop_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id to stop tracking, 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.7/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds what annotations cannot: the job keeps running and tempolor_get_music still reads the track, only replyUrl callbacks cease, the maxJobs slot is freed, and a 404 is returned for untracked jobs. That is the exact side-effect profile an agent needs before an irreversible call.

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?

Front-loads the action and its effect, then the crucial non-effect, then the failure mode, then the endpoint. Every clause carries decision-relevant information and none of it is restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one parameter, full schema coverage, and rich annotations, the remaining burden is behavioral and provenance detail, both of which are provided. No output schema exists, yet the error condition (404) is still disclosed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by stating where the job_id comes from (tempolor_list_running_jobs) and that it names the account. The format example itself lives in the schema, not the description.

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 ('Stop this API tracking a running job') and immediately scopes what is stopped versus what continues at TemPolor. It explicitly distinguishes this from cancelling the underlying job, so an agent can tell it apart from deletion-style siblings like tempolor_delete_music.

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?

Gives clear preconditions: the job_id must come from tempolor_list_running_jobs and the job must currently be tracked, otherwise 404. It also clarifies the misleading case (this is not a job cancellation), which prevents a common misuse. It stops short of naming an explicit alternative for actually cancelling or removing a job.

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