Skip to main content
Glama

poll_hunyuan_job_status

Poll a Hunyuan3D generation job for completion. Returns the generated model path when status is DONE.

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?

With no annotations, the description carries full burden. It discloses the polling nature, possible statuses ('DONE', 'RUN', failed), and that a 'DONE' response includes ResultFile3Ds with a ZIP path. It does not mention error handling or timeouts, but overall gives a clear behavioral picture.

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?

The description is front-loaded with the purpose, then details parameters, return values, and a usage note. It is slightly redundant (ResultFile3Ds mentioned twice) but overall efficient. Could be shortened without losing meaning.

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 polling status tool with one parameter and no output schema, the description covers the key aspects: what it does, how to use it, status values, and expected output. It lacks differentiation from get_hunyuan3d_status and does not mention error states, but is sufficiently complete for its simplicity.

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?

The schema has 0% coverage with no description for job_id, but the description fully explains it as 'The job_id given in the generate model step.' This adds essential meaning beyond the schema's type only, fully compensating for the missing schema description.

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, specifying verb 'Check' and resource 'Hunyuan3D generation task'. It distinguishes from siblings by noting it's a polling API, which differentiates it from non-polling status tools like get_hunyuan3d_status.

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?

The description explains it is a polling API and advises to only proceed when status is final ('DONE' or failed). It indicates the job_id comes from the generate step. However, it does not explicitly tell when not to use it (e.g., vs. get_hunyuan3d_status) which would strengthen guidance.

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/naab007/blender_mcp'

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