Skip to main content
Glama

transcribe_cancel_job

Cancel an ongoing asynchronous transcription job by providing its job ID.

Instructions

Cancel an async transcription job (best-effort).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Implementation Reference

  • Handler function for the transcribe_cancel_job tool. Calls transcribeJobManager.cancelJob() and returns the result as JSON.
    private async handleTranscribeCancelJob(args: {
      job_id: string;
    }): Promise<{ content: Array<{ type: string; text: string }> }> {
      const ok = this.transcribeJobManager.cancelJob(args.job_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({ ok }, null, 2),
          },
        ],
      };
    }
  • Tool registration with inputSchema: requires a single 'job_id' string property.
    name: "transcribe_cancel_job",
    description: "Cancel an async transcription job (best-effort).",
    inputSchema: {
      $schema: "https://json-schema.org/draft/2020-12/schema",
      type: "object",
      properties: { job_id: { type: "string" } },
      required: ["job_id"],
      additionalProperties: false,
    },
  • src/index.ts:350-357 (registration)
    ListToolsRequestSchema handler that registers the transcribe_cancel_job tool in the tools array.
    $schema: "https://json-schema.org/draft/2020-12/schema",
    type: "object",
    properties: {
      upload_id: { type: "string" },
      skip_compression: { type: "boolean" },
      engine: { type: "string", enum: ["openai", "local", "auto"] },
      language: { type: "string" },
      as_text: { type: "boolean" },
  • src/index.ts:484-487 (registration)
    CallToolRequestSchema case statement dispatching 'transcribe_cancel_job' to handleTranscribeCancelJob.
    case "transcribe_cancel_job":
      return await this.handleTranscribeCancelJob(
        args as { job_id: string },
      );
  • The cancelJob() method in TranscribeJobManager. Sets the job's 'cancelled' flag to true (best-effort cancellation).
    cancelJob(id: string): { ok: boolean } {
      const job = this.jobs.get(id);
      if (!job) return { ok: false };
      job.cancelled = true;
      return { ok: true };
    }
Behavior2/5

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

The phrase 'best-effort' hints at non-guaranteed success, but no disclosure of side effects, what happens if job already complete, or required permissions. Annotations absent, so description carries full burden but is insufficient.

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?

Extremely concise: one short phrase with no filler. Every word earns its place.

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

Completeness2/5

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

For a simple cancellation tool with one parameter and no output schema, the description lacks completeness: no indication of return value (e.g., success/failure message), no error states, and no confirmation that the job was cancelled. The 'best-effort' is the only extra context.

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

Parameters1/5

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

Single parameter job_id with 0% schema description coverage. Description does not explain the parameter (format, source, or how to obtain it). Fails to add meaning beyond the schema.

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?

The description 'Cancel an async transcription job (best-effort)' clearly identifies the action (cancel) and the resource (async transcription job). It distinguishes from siblings like transcribe_get_job (status check) and upload tools, but doesn't explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives (e.g., checking job status first). No mention of context like job must be in progress.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JamesANZ/transcript-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server