Skip to main content
Glama

Get Transcription Job Status

get_transcription_status
Read-only

Poll transcription progress and retrieve completed results using the job ID returned by transcribe_audio_url.

Instructions

Poll GhostMinutes for transcription progress and results using job_id returned by transcribe_audio_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesjob_id returned by transcribe_audio_url

Implementation Reference

  • The handler function for get_transcription_status. Calls client.getJobStatus(job_id) and returns the result as both text and structured content.
      async ({ job_id }) => {
        const body = await client.getJobStatus(job_id);
        return {
          content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
          structuredContent: jsonStructured(body),
        };
      },
    );
  • Registration of the tool 'get_transcription_status' on the MCP server with input schema requiring a job_id string.
      server.registerTool(
        'get_transcription_status',
        {
          title: 'Get Transcription Job Status',
          description:
            'Poll GhostMinutes for transcription progress and results using job_id returned by transcribe_audio_url.',
          inputSchema: z.object({
            job_id: z.string().min(1).describe('job_id returned by transcribe_audio_url'),
          }),
          annotations: { readOnlyHint: true, openWorldHint: true },
        },
        async ({ job_id }) => {
          const body = await client.getJobStatus(job_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(body, null, 2) }],
            structuredContent: jsonStructured(body),
          };
        },
      );
    }
  • Input schema for get_transcription_status: requires a single 'job_id' string parameter.
    inputSchema: z.object({
      job_id: z.string().min(1).describe('job_id returned by transcribe_audio_url'),
    }),
  • Helper method on GhostMinutesClient that makes a GET request to /mcp/status/{jobId} to retrieve transcription status.
    async getJobStatus(jobId: string): Promise<unknown> {
      try {
        const res = await this.http.get(`/mcp/status/${encodeURIComponent(jobId)}`, {
          headers: this.hasApiKey()
            ? { Authorization: `Bearer ${this.apiKey}` }
            : {},
        });
        return this.ensureOk(res);
      } catch (e) {
        this.handleThrown(e);
      }
    }
  • Utility function that coerces arbitrary JSON-compatible values into MCP structuredContent shape.
    export function jsonStructured(body: unknown): Record<string, unknown> {
      try {
        const cloned: unknown = JSON.parse(JSON.stringify(body));
        if (cloned && typeof cloned === 'object' && !Array.isArray(cloned)) {
          return cloned as Record<string, unknown>;
        }
        return { value: cloned };
      } catch {
        return { result: String(body) };
      }
    }
Behavior4/5

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

Describes polling behavior and that it returns progress and results, complementing readOnlyHint and openWorldHint annotations. No contradictions.

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?

Single sentence with clear verb (Poll) and resource (transcription progress/results). No extraneous text.

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

Completeness3/5

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

Functional but lacks detail on return structure (e.g., progress fields, result format) given no output schema. Adequate for basic usage.

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 coverage is 100% and description adds no extra meaning beyond schema's job_id description. Baseline 3 applies.

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?

Clearly specifies polling for transcription progress/results using job_id from transcribe_audio_url. Differentiates from siblings like transcribe_audio_url (creation) and get_transcript (final output).

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 states prerequisite: job_id from transcribe_audio_url, implying post-creation usage. Lacks explicit when-not-to-use or alternatives like get_transcript, but context is clear.

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/Rocketech-Software-Development/ghostminutes-mcp'

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