Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Generate Image

generate_image

Create an AI image from a prompt and save it to your AdaptlyPost image studio, returning a job ID to poll for the finished image URL ready for post creation.

Instructions

Create an image from the user's prompt with AdaptlyPost AI and save it to the user's own AI image studio in AdaptlyPost. Nothing is posted. It returns { jobId, sessionId, status } right away with status queued; poll get_image_job with the jobId every few seconds until status is completed or failed (usually 10 to 40 seconds). A completed job carries imageUrl, which can go straight into mediaUrls of create_post. Reuse sessionId to keep related images together. Needs the ai.generate permission, which Admin, Editor and Contributor hold and Viewer does not (403 permission_denied). Uses the member's AdaptlyPost AI credits (2 for standard, 4 for premium, none when the member connected their own image provider key) and refunds them if the job fails. With no credits left the job fails with an error saying so; tell the user and do not retry.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNostandard (default, 2 credits) or premium (higher fidelity, 4 credits)
promptYesWhat the image should show, including style and composition
qualityNoRendering quality, used only when the member generates with their own OpenAI key. Omit for medium. AdaptlyPost's standard and premium models and a Google key ignore it
sessionIdNoImage studio session to add the image to, as returned by an earlier generate_image. Omit to start a new session
aspectRatioNoImage shape (default 1:1). Pick one that suits the target platform, e.g. 9:16 for stories and reels, 4:5 for Instagram feed, 16:9 for YouTube and X
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
referenceImagesNoImage URLs the user provided, such as publicUrl values from upload_media, to guide the style or subject

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with jobId (pass it to get_image_job), sessionId, and status (queued).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the supplied annotations (openWorldHint, idempotentHint=false, destructiveHint=false) by disclosing that the call is asynchronous, returns a queued envelope immediately, and completes in 10-40 seconds. It quantifies credit consumption (2 standard / 4 premium / 0 with own key), states refunds on failure, and pins the authorization profile (Admin/Editor/Contributor yes, Viewer 403 permission_denied). None of this contradicts the annotations.

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?

Front-loaded with purpose and the "nothing is posted" clarification, then proceeds through return shape, polling, session reuse, permissions, and billing in a sensible order. It is a dense single block rather than scannable bullets, and a couple of clauses (credit refund details) could be tightened, but no sentence is filler.

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?

For a 7-parameter async generation tool with an output schema, the definition covers everything an agent needs to call it correctly: required prompt, model/credit tradeoff, session grouping, aspect-ratio selection by platform, permissions, failure and no-retry behavior, and the next step after completion.

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 description coverage is 100%, so the schema already carries per-parameter meaning and the baseline is 3. The description still adds usage-level semantics the schema cannot: reuse sessionId to keep related images together, and that imageUrl flows into create_post. Marginal but real value beyond structured fields.

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 ("Create an image from the user's prompt with AdaptlyPost AI") plus the destination (the user's AI image studio), and immediately disambiguates from the sibling create_post with "Nothing is posted." An agent can distinguish this from get_image_job, generate_caption, and create_post 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 Guidelines5/5

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

Gives explicit follow-up procedure (poll get_image_job every few seconds until completed or failed, typically 10-40 seconds) and names the exact next step for the output (imageUrl into mediaUrls of create_post). Also states when NOT to retry (no credits remaining) and warns of the 403 permission_denied case for Viewers, which is genuine routing guidance.

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