Skip to main content
Glama
supadata-ai

Supadata

by supadata-ai

supadata_check_transcript_status

Check the status of a transcript job to monitor progress and retrieve results when ready.

Instructions

Check transcript job status and retrieve results. Returns status: "queued", "active", "completed", or "failed". If status is not "completed" or "failed", call this tool again after a few seconds with the same id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler implementation for the supadata_check_transcript_status tool.
    handler: async (args: any, apiKey: string) => {
      const id = args.id;
      const result = await callSupadata(`/transcript/${id}`, {}, apiKey, 'GET');
      return addPollingHint(result, 'supadata_check_transcript_status', id);
    },
  • The schema definition for the supadata_check_transcript_status tool.
    schema: {
      name: 'supadata_check_transcript_status',
      description: 'Check transcript job status and retrieve results. Returns status: "queued", "active", "completed", or "failed". If status is not "completed" or "failed", call this tool again after a few seconds with the same id.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
        },
        required: ['id'],
      },
    },
  • src/mcp.ts:98-115 (registration)
    The full tool registration block for supadata_check_transcript_status.
    supadata_check_transcript_status: {
      schema: {
        name: 'supadata_check_transcript_status',
        description: 'Check transcript job status and retrieve results. Returns status: "queued", "active", "completed", or "failed". If status is not "completed" or "failed", call this tool again after a few seconds with the same id.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string' },
          },
          required: ['id'],
        },
      },
      handler: async (args: any, apiKey: string) => {
        const id = args.id;
        const result = await callSupadata(`/transcript/${id}`, {}, apiKey, 'GET');
        return addPollingHint(result, 'supadata_check_transcript_status', id);
      },
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's polling behavior, return values (status enum), and retry logic. It doesn't mention error handling, rate limits, or authentication requirements, but provides substantial operational context for a status-checking tool.

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?

The description is perfectly concise with two sentences that each serve distinct purposes: the first states the core functionality, the second provides critical usage guidance. There is zero wasted text, and the information is front-loaded with the most important details first.

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 single-parameter status-checking tool with no annotations or output schema, the description provides excellent coverage of the core functionality, return values, and polling behavior. It doesn't specify what 'results' means when status is 'completed' or error details for 'failed' status, but gives sufficient context for effective agent usage.

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?

With 0% schema description coverage for the single parameter, the description adds crucial context by implying the 'id' parameter should be reused for polling ('call this tool again after a few seconds with the same id'). While it doesn't specify the id format or source, it provides meaningful guidance about parameter usage in the polling workflow.

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?

The description clearly states the tool's purpose with specific verbs ('check transcript job status and retrieve results') and distinguishes it from siblings by focusing on transcript jobs specifically. It identifies the exact resource being checked (transcript job 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 Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('If status is not "completed" or "failed", call this tool again after a few seconds with the same id') and distinguishes it from alternatives by specifying it's for transcript jobs only. The retry guidance is particularly valuable for polling scenarios.

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/supadata-ai/mcp'

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