Skip to main content
Glama

poll_hunyuan_job_status

Poll the status of a Hunyuan3D generation job using its job ID. Returns the generated 3D model ZIP path when the task is complete.

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
Behavior5/5

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

With no annotations, the description fully covers behavior: it explains the polling nature, possible statuses (DONE, RUN, failed states), and the response structure (ResultFile3Ds with ZIP path). This transparently sets expectations for the agent.

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 well-structured with a clear intro and parameter/response details. It uses bullet points, though some sentences are longer than necessary. Overall efficient and front-loaded with purpose.

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 no output schema, the description adequately explains return values (status and ResultFile3Ds). It covers polling semantics and status transitions. Minor gap: failed states are not elaborated, but basic completeness is met.

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?

Schema coverage is 0%, so description must detail the parameter. It explains job_id as 'The job_id given in the generate model step,' adding context beyond the schema's title. Though brief, it sufficiently describes the single parameter's origin and role.

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: 'Check if the Hunyuan3D generation task is completed.' It specifies the resource (Hunyuan3D generation task) and the action (poll status), distinguishing it from sibling polling tools like poll_rodin_job_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 when to use the tool: after a generate model step, and to check if the task is done. It advises to only proceed when status is final. However, it does not explicitly mention when not to use or alternatives, leaving implicit 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/AaronBrunckhurst/blender-mcp-2.79'

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