adsoptimiser_get_jobCheck the status of an image or video generation job and retrieve its result URL once processing finishes. Pass the job ID to see whether a creative is queued, ready, failed, or expired.
Get the status of an image or video job, with the result URL once it is ready (statuses: queued, generating, ready, failed, expired).
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds the full status lifecycle (queued, generating, ready, failed, expired) and notes that the result URL appears once ready, which is useful behavioral context beyond what the annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the core action and outcome, and the parenthetical status list is efficient. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers the return value (result URL) despite no output schema, and enumerates statuses. Missing is any indication of where job_id comes from or what happens when a job fails or expires, which leaves an agent without full context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description never mentions job_id or how to obtain it. For the single required parameter, the description offers no format, pattern, or sourcing details, so it fails to compensate for the missing schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Get' and resource 'status of an image or video job', and lists the possible statuses. It does not explicitly distinguish itself from sibling tools like download_job or list_jobs, but the scope is clear enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus list_jobs (to find jobs) or download_job (to fetch the asset). Usage is implied—poll a job by ID—but no prerequisites or alternatives are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.