Skip to main content
Glama
gaudiolab-jp

gaudio-developers-mcp

Official

gaudio_get_job

Retrieve job status and results for audio processing. Input job ID and model to view waiting, running, success, or failed status.

Instructions

Check job status and get results. Status: 'waiting' (queued), 'running' (processing), 'success' (done, downloadUrl included), 'failed' (error). Download URLs expire after 48 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesJob ID from gaudio_create_job or gaudio_separate_audio
modelYesModel name used to create the job

Implementation Reference

  • Main handler for 'gaudio_get_job' tool. Registers the tool on the MCP server, validates inputs with Zod schema (jobId, model), looks up model info, calls client.getJob() to check status, and returns a formatted response with jobId, model, status, and optionally downloadUrl (success) or errorMessage (failed).
    export function registerGetJob(server: McpServer, client: GaudioClient) {
      server.tool(
        "gaudio_get_job",
        "Check job status and get results. Status: 'waiting' (queued), 'running' (processing), 'success' (done, downloadUrl included), 'failed' (error). Download URLs expire after 48 hours.",
        {
          jobId: z.string().describe("Job ID from gaudio_create_job or gaudio_separate_audio"),
          model: z.string().describe("Model name used to create the job"),
        },
        async ({ jobId, model }) => {
          const modelInfo = getModel(model);
          if (!modelInfo) {
            return {
              content: [{ type: "text" as const, text: `Unknown model: ${model}` }],
              isError: true,
            };
          }
    
          const res = await client.getJob(model, jobId);
          const data = res.resultData ?? {};
    
          const result: Record<string, unknown> = {
            jobId,
            model,
            status: data.status,
          };
    
          if (data.status === "success") {
            result.downloadUrl = data.downloadUrl;
            result.expireAt = data.expireAt;
          } else if (data.status === "failed") {
            result.errorMessage = data.errorMessage;
          }
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        },
      );
  • Zod input schema for 'gaudio_get_job': requires jobId (string) and model (string) parameters.
    {
      jobId: z.string().describe("Job ID from gaudio_create_job or gaudio_separate_audio"),
      model: z.string().describe("Model name used to create the job"),
    },
  • src/index.ts:30-30 (registration)
    Registration call: registerGetJob(server, client) invoked in the main entry point to register the tool on the MCP server.
    registerGetJob(server, client);
  • API client helper: getJob() sends a GET request to /{model}/jobs/{jobId} and returns the raw API response.
      async getJob(model: string, jobId: string): Promise<ApiResponse> {
        return this.request("GET", `/${model}/jobs/${jobId}`);
      }
    
      async getKeyInfo(): Promise<ApiResponse> {
        return this.request("GET", "/key/info");
      }
    }
  • getModel() helper used by the handler to validate that the model name exists in the registry.
    export function getModel(name: string): ModelInfo | undefined {
      return MODEL_REGISTRY.find((m) => m.name === name);
    }
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the polling nature, status states, and URL expiration, but does not mention authentication or request limits. It is adequate but not comprehensive.

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?

Two concise sentences pack the essential information: purpose, status states, and download URL expiration. No superfluous content.

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 simple status-checking tool with two required parameters and no output schema, the description covers key aspects: status enumeration, URL expiration, and result availability. Could mention that results are included on success, but overall complete.

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?

Input schema covers both parameters with descriptions (100% coverage). The description adds value by indicating that jobId comes from specific creation tools (gaudio_create_job or gaudio_separate_audio), which is helpful context beyond the schema.

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 as checking job status and retrieving results, and lists possible statuses with outcomes. This distinguishes it from sibling tools like gaudio_create_job (creation) or gaudio_list_models (listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage after job creation but does not explicitly state when to use this tool versus alternatives or provide exclusions. It does include a useful note about download URL expiration.

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/gaudiolab-jp/gaudio-developers-mcp'

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