Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Get Image Job

get_image_job
Read-onlyIdempotent

Polls the status of an image generation job until it completes or fails, returning the resulting public image URL ready for use in social media posts, or the error reason if it failed.

Instructions

Read the state of an image started with generate_image. Returns { jobId, sessionId, status, imageUrl, imageId, error }; status moves from queued through processing and generating to completed or failed. When completed, imageUrl is a public URL ready for mediaUrls in create_post. When failed, error says why, for example no credits left; a failed job is final, so do not poll it again. Poll every few seconds while status is queued, processing or generating, and stop after a couple of minutes. Only jobs started by the same member are visible. Needs the ai.generate permission, which Admin, Editor and Contributor hold and Viewer does not (403 permission_denied). Reading a job spends no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobId": "<jobId>"
    },
    "name": "get_image_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesjobId returned by generate_image
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with jobId, sessionId, status (queued, processing, generating, completed or failed), imageUrl (null until completed), imageId, and error (null unless failed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, yet the description still adds substantial context beyond them: the status state machine, that a failed job is terminal, the specific error example (no credits), the member-scoped visibility rule, the required ai.generate permission with role coverage and the 403 permission_denied shape, and the fact that reading spends no credits. That last point is exactly the kind of side-effect disclosure an agent needs before polling in a loop.

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?

Front-loaded with purpose, then return shape, lifecycle, polling cadence, visibility, permissions. Each sentence contributes operational detail an agent would otherwise have to guess, and there is no filler or restatement of the name.

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?

Covers everything needed to call and loop this tool correctly: what it reads, how status evolves, when to stop polling, what errors mean, who can call it, and what the output is used for downstream. The output schema exists, yet the description's return-shape summary still usefully frames the fields it references.

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?

Schema description coverage is 100% and both parameters (jobId, workspaceId) are documented in the schema, so the baseline applies. The description does not add syntax or sourcing detail for jobId beyond what the schema states, leaving the structured fields to carry parameter meaning.

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?

Opens with a specific verb+resource pair ('Read the state of an image started with generate_image') and explicitly anchors the tool to the sibling that creates the job. An agent can immediately tell this is the polling counterpart to generate_image, not a generic job or image tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance at each lifecycle state: poll every few seconds while queued/processing/generating, stop after a couple of minutes, and do not re-poll a failed job because failure is final. It also names the downstream step (imageUrl feeds mediaUrls in create_post), which tells the agent where this fits in a workflow.

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