Skip to main content
Glama

poll_hunyuan_job_status

Check completion status of a Hunyuan3D generation job. Poll with the job ID until status is 'DONE' to retrieve the generated 3D model ZIP path.

Instructions

Check if the Hunyuan3D generation task is completed.

For Hunyuan3D: Parameters: - job_id: The job_id given in the generate model step.

Returns the generation task status. The task is done if status is "DONE".
The task is in progress if status is "RUN".
If status is "DONE", returns ResultFile3Ds, which is the generated ZIP model path
When the status is "DONE", the response includes a field named ResultFile3Ds that contains the generated ZIP file path of the 3D model in OBJ format.
This is a polling API, so only proceed if the status are finally determined ("DONE" or some failed state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idNo
Behavior4/5

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

No annotations provided, so description fully carries the burden. Discloses status values (DONE, RUN), return format (ResultFile3Ds with ZIP path), and polling behavior. Lacks details on rate limits or auth needs but is solid overall.

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?

Description is informative but slightly redundant, repeating status meanings and return format. Could be more concise without losing clarity.

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?

Given one parameter and no output schema, the description explains return values, status conditions, and polling nature. Lacks detail on error states or timeout, but adequately comprehensive for a polling tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter job_id has no schema description (0% coverage), but the description adds that it is the job_id from the generate model step, providing essential context beyond the schema's title and default.

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 checks if the Hunyuan3D generation task is completed, using a specific verb (check/completion) and resource (Hunyuan3D task). It distinguishes from siblings like poll_rodin_job_status by naming the specific model.

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 this is a polling API and to only proceed when status is final. Provides context on using job_id from the generation step. Does not explicitly list when not to use or alternatives.

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/silwings1986/blender-mcp'

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