Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get render job

get_job
Read-onlyIdempotent

Poll a render job by id to get status, progress, and media URL when done. Stop polling on not_found or error to avoid double-charging.

Instructions

Poll a render job by id. Returns status (queued|running|done|error), progress, and on done the served media URL. Renders take 1–3 minutes: keep calling this until done/error without asking the user — several calls is normal, not a stall. An id that does not exist on this account answers status "not_found" — that is FINAL: stop polling it, and do not re-fire the render (that double-charges).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesthe job id, e.g. job_xxx

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "error": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the failure message when status is error"
-    },
-    "id": {
-      "description": "the job id",
-      "type": "string"
-    },
-    "progress": {
-      "description": "0–1 progress when reported",
-      "type": "number"
-    },
-    "result": {
-      "description": "the raw job result payload"
-    },
-    "status": {
-      "description": "queued | running | done | error",
-      "type": "string"
-    },
-    "type": {
-      "description": "the job type (video / stitch / avatar / …)",
-      "type": "string"
-    },
-    "url": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the served media URL once done"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.15
  3. Removedv0.1.0
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real operational context: expected latency, that repeated polling is intended rather than a stall, that 'not_found' is terminal, and that re-firing a render double-charges. That cost/consequence disclosure is exactly the value structured fields cannot carry.

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?

Four sentences, front-loaded with the verb and return shape, then the polling contract and the failure semantics in descending order of importance. No filler; each sentence changes agent behavior.

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?

There is no output schema, but the description names the return fields and their enum-ish values (queued|running|done|error), progress, and the served media URL, so the agent knows what to expect. Combined with the polling and terminal-state rules, nothing needed to call this correctly is missing.

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?

Only one parameter, and schema description coverage is 100% ('the job id, e.g. job_xxx'), so the schema already documents it. The description adds no format or sourcing detail beyond 'by id', which matches the baseline-3 case where the schema does the heavy lifting.

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?

States a specific verb and resource ('Poll a render job by id') and immediately scopes what it returns (status, progress, served media URL). This is clearly distinguishable from siblings like list_jobs (enumeration) and render_ad (creation) without opening any schema.

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?

Gives strong operating context: renders take 1–3 minutes, keep polling until done/error, don't ask the user, several calls are normal. The 'when not' case is also explicit (stop on not_found, don't re-fire). It does not name a sibling for discovering job ids, which is the only gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools