Skip to main content
Glama

Get Hedra Job Result

hedra_get_job
Read-onlyIdempotent

Retrieve a completed job's full result envelope, including downloadable output URLs and asset IDs, or the error if it failed. Use it to get the final generated file or diagnose why a job failed.

Instructions

Fetch the full result envelope for a job, including its outputs (with download URLs and asset_ids) once complete, or its error if it failed.

Use this to retrieve the final generated file's URL, or the failure reason for a FAILED job. For a lighter-weight progress check while a job is still running, use hedra_get_job_status instead — or use hedra_wait_for_job to block until it finishes.

Args:

  • job_id (string, required): the job id returned by hedra_submit_job (format job_).

Returns: JSON {job_id, model, status, outputs: [{url, asset_id, content_type, ...}], error, created_at, updated_at}. outputs[].url is the downloadable result; outputs[].asset_id can be fed back into another model's input as {"source":"asset","asset_id":...}.

Error Handling:

  • "Error [NOT_FOUND]: Job not found." — double check the job_id, or that it belongs to this API key's workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe job's id, formatted job_<uuid> — returned by hedra_submit_job.
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive. Description adds meaningful behavioral context: return envelope structure, error format, and how asset_id can be reused as input to other models. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections: purpose, usage guidance, args, returns, error handling. All sentences are informative, though slightly verbose for the amount of unique content.

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

Completeness5/5

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

No output schema exists, so description correctly details the return JSON structure including outputs[].url and outputs[].asset_id, plus error handling. Covers both success and failure modes fully.

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 description covers 100% of parameter semantics (format and origin of job_id). Description reiterates this but doesn't add new syntax details, so baseline 3 is appropriate.

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?

Description begins with 'Fetch the full result envelope for a job', clearly stating the verb and resource. It distinguishes itself from siblings by contrasting with hedra_get_job_status and hedra_wait_for_job.

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?

Explicitly states when to use this tool vs alternatives: use hedra_get_job_status for lighter progress checks and hedra_wait_for_job to block. Also provides error handling guidance for job not found.

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/HemanthDonga/hedra-mcp-server'

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