Skip to main content
Glama

transcribe_get_job

Poll an audio transcription job and fetch the transcript upon completion.

Instructions

Poll an async transcription job created by transcribe-audio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
as_textNo

Implementation Reference

  • src/index.ts:364-391 (registration)
    Registration and input schema for the transcribe_get_job tool in the MCP tools list definition.
        {
          name: "transcribe_get_job",
          description:
            "Poll an async transcription job created by transcribe-audio.",
          inputSchema: {
            $schema: "https://json-schema.org/draft/2020-12/schema",
            type: "object",
            properties: {
              job_id: { type: "string" },
              as_text: { type: "boolean" },
            },
            required: ["job_id"],
            additionalProperties: false,
          },
        },
        {
          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,
          },
        },
      ],
    }));
  • Handler for transcribe_get_job: retrieves a job from TranscribeJobManager and returns completed result (formatted) or current job status.
    private async handleTranscribeGetJob(args: {
      job_id: string;
      as_text?: boolean;
    }): Promise<{ content: Array<{ type: string; text: string }> }> {
      const job = this.transcribeJobManager.getJob(args.job_id);
      if (job.status === "completed" && job.result) {
        return {
          content: [
            {
              type: "text",
              text: this.formatTranscriptionPayload(
                job.result,
                args.as_text,
                false,
              ),
            },
          ],
        };
      }
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(job, null, 2),
          },
        ],
      };
    }
  • TranscribeJobManager.getJob() - retrieves async job status/result used by handleTranscribeGetJob.
    getJob(id: string): {
      status: JobStatus | "unknown";
      result?: StructuredTranscriptionResult;
      error?: string;
    } {
      this.gcOldJobs();
      const job = this.jobs.get(id);
      if (!job) return { status: "unknown", error: "Unknown job_id" };
      if (job.status === "processing") {
        return { status: "processing" };
      }
      if (job.status === "cancelled") {
        return { status: "cancelled", error: "Job was cancelled." };
      }
      if (job.status === "failed") {
        return { status: "failed", error: job.error || "Job failed." };
      }
      return { status: "completed", result: job.result };
    }
  • Input schema for transcribe_get_job: requires job_id (string), optional as_text (boolean).
    inputSchema: {
      $schema: "https://json-schema.org/draft/2020-12/schema",
      type: "object",
      properties: {
        job_id: { type: "string" },
        as_text: { type: "boolean" },
      },
      required: ["job_id"],
      additionalProperties: false,
    },
  • Helper used by handleTranscribeGetJob to format completed job result as text with timestamps, plain text, or JSON.
    private formatTranscriptionPayload(
      payload: StructuredTranscriptionResult | TranscribeAsyncQueued,
      asText: boolean | undefined,
      includeTimestamps: boolean | undefined,
    ): string {
      if ("job_id" in payload) {
        return JSON.stringify(payload, null, 2);
      }
      if (asText) {
        if (includeTimestamps) {
          return this.formatTranscript(
            payload.segments.map((segment) => ({
              text: segment.text,
              start: segment.start,
              duration: Math.max(0, segment.end - segment.start),
            })),
            true,
          );
        }
        return payload.text;
      }
      return JSON.stringify(payload, null, 2);
    }
Behavior2/5

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

The description mentions 'async' but does not elaborate on typical async polling behavior: whether the tool is non-blocking, what happens if the job is not ready (error or empty response), or any side effects. It also lacks information about rate limits or read-only status.

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 description is a single sentence, which is concise but lacks critical details. While it is front-loaded with the action, it does not earn its place fully because it omits information that would make the tool usable.

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?

Given the complexity of an async polling tool (2 parameters, no output schema, no annotations), the description is insufficient. It does not describe response structure, polling behavior, error handling, or how to interpret results. The tool's behavior is largely opaque.

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?

With 0% schema description coverage, the description adds no meaning beyond the parameter names. 'job_id' is implied to be an identifier but not explained; 'as_text' is not described at all (e.g., whether it controls output format). This fails to compensate for the missing schema descriptions.

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 clearly states the action ('poll') and the resource ('async transcription job'), and references the creation tool 'transcribe-audio' for context. However, it does not specify what information is returned upon polling (e.g., status, results).

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 is provided on when to use this tool versus siblings like transcribe_cancel_job. There is no mention of polling frequency, when a job is considered complete, or prerequisites such as obtaining a job_id from transcribe-audio.

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