Skip to main content
Glama

post-controlnet-inferences

Generate AI images guided by control inputs like poses, edges, or depth maps to maintain specific structural elements in the output.

Instructions

Trigger a new image generation in ControlNet mode. The control image is used to guide the generation; it can be a pose, canny map, or similar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalAssetsNoIf set to true, returns the original asset without transformation
dryRunNo
controlEndNoSpecifies how long the ControlNet guidance should be applied during the inference process. Only available for Flux.1-dev based models. The value represents the percentage of total inference steps where the ControlNet guidance is active. For example: - 1.0: ControlNet guidance is applied during all inference steps - 0.5: ControlNet guidance is only applied during the first half of inference steps Default values: - 0.5 for Canny modality - 0.6 for all other modalities
modalityYesThe modality associated with the control image used for the generation: it can either be an object with a combination of maximum For models of SD1.5 family: - up to 3 modalities from `canny`, `pose`, `depth`, `lines`, `seg`, `scribble`, `lineart`, `normal-map`, `illusion` - or one of the following presets: `character`, `landscape`, `city`, `interior`. For models of the SDXL family: - up to 3 modalities from `canny`, `pose`, `depth`, `seg`, `illusion`, `scribble` - or one of the following presets: `character`, `landscape`. For models of the FLUX schnell or dev families: - one modality from: `canny`, `tile`, `depth`, `blur`, `pose`, `gray`, `low-quality` Optionally, you can associate a value to these modalities or presets. The value must be within `]0.0, 1.0]`. Examples: - `canny` - `depth:0.5,pose:1.0` - `canny:0.5,depth:0.5,lines:0.3` - `landscape` - `character:0.5` - `illusion:1` Note: if you use a value that is not supported by the model family, this will result in an error.
seedNoUsed to reproduce previous results. Default: randomly generated number.
modelIdYesThe model id to use for the inference
schedulerNoThe scheduler to use to override the default configured for the model. See detailed documentation for more details.
disableModalityDetectionNoIf false, the process uses the given image to detect the modality. If true (default), the process will not try to detect the modality of the given image. For example: with `pose` modality and `false` value, the process will detect the pose of people in the given image with `depth` modality and `false` value, the process will detect the depth of the given image with `scribble` modality and `true`value, the process will use the given image as a scribble ⚠️ For models of the FLUX schnell or dev families, this parameter is ignored. The modality detection is always disabled. ⚠️
imageParentIdNoSpecifies the parent asset Id for the image when provided as a dataurl.
baseModelIdNoThe base model to use for the inference. Only Flux LoRA models can use this parameter. Allowed values are available in the model's attribute: `compliantModelIds`
controlStartNoSpecifies the starting point of the ControlNet guidance during the inference process. Only available for Flux.1-dev based models. The value represents the percentage of total inference steps where the ControlNet guidance starts. For example: - 0.0: ControlNet guidance starts at the beginning of the inference steps - 0.5: ControlNet guidance starts at the middle of the inference steps
heightNoThe height of the generated images, must be a 8 multiple (within [64, 2048], default: 512) If model.type is `sd-xl`, `sd-xl-lora`, `sd-xl-composition` the height must be within [512, 2048] If model.type is `sd-1_5`, the height must be within [64, 1024] If model.type is `flux.1.1-pro-ultra`, you can use the aspectRatio parameter instead
imageHideNoToggles the hidden status of the image when provided as a dataurl.
controlImageIdNoThe controlnet input image as an AssetId. Will be ignored if the `controlnet` parameter is provided
imageNoThe input image as a data URL (example: "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVQYV2NgYAAAAAMAAWgmWQ0AAAAASUVORK5CYII=") or the asset ID (example: "asset_GTrL3mq4SXWyMxkOHRxlpw")
imageIdNoDeprecated: The input image as an AssetId. Prefer to use image with the asset ID instead.
modelEpochNoThe epoch of the model to use for the inference. Only available for Flux Lora Trained models.
hideResultsNoIf set, generated assets will be hidden and not returned in the list of images of the inference or when listing assets (default: false)
negativePromptNoThe prompt not to guide the image generation, ignored when guidance < 1 (example: "((ugly face))") For Flux based model (not Fast-Flux): requires negativePromptStrength > 0 and active only for inference types txt2img / img2img / controlnet.
intermediateImagesNoEnable or disable the intermediate images generation (default: false)
conceptsNo
controlImageNoThe controlnet input image as a data URL (example: "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVQYV2NgYAAAAAMAAWgmWQ0AAAAASUVORK5CYII=")
guidanceNoControls how closely the generated image follows the prompt. Higher values result in stronger adherence to the prompt. Default and allowed values depend on the model type: - For Flux dev models, the default is 3.5 and allowed values are within [0, 10] - For Flux pro models, the default is 3 and allowed values are within [2, 5] - For SDXL models, the default is 6 and allowed values are within [0, 20] - For SD1.5 models, the default is 7.5 and allowed values are within [0, 20]
numInferenceStepsNoThe number of denoising steps for each image generation (within [1, 150], default: 30)
numSamplesNoThe number of images to generate (within [1, 128], default: 4)
widthNoThe width of the generated images, must be a 8 multiple (within [64, 2048], default: 512) If model.type is `sd-xl`, `sd-xl-lora`, `sd-xl-composition` the width must be within [512, 2048] If model.type is `sd-1_5`, the width must be within [64, 1024] If model.type is `flux.1.1-pro-ultra`, you can use the aspectRatio parameter instead
negativePromptStrengthNoOnly applicable for flux-dev based models for `txt2img`, `img2img`, and `controlnet` inference types. Controls the influence of the negative prompt. Default 0 means the negative prompt has no effect. Higher values increase negative prompt influence. Must be > 0 if negativePrompt is provided.
promptYesFull text prompt including the model placeholder. (example: "an illustration of phoenix in a fantasy world, flying over a mountain, 8k, bokeh effect")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'triggers a new image generation' which implies a write/mutation operation, but doesn't disclose important behavioral traits like whether this is an asynchronous operation, what permissions are required, rate limits, or what happens to the generated images. The description is too brief to adequately cover behavioral aspects for a complex image generation tool.

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?

The description is extremely concise - just two sentences that directly state the tool's purpose. It's front-loaded with the core functionality and wastes no words. Every sentence earns its place by explaining what the tool does and how the control image functions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 28 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how to handle the generated images, error conditions, or important behavioral aspects. The high parameter count and complexity demand more comprehensive guidance that the brief description doesn't provide.

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?

The schema description coverage is 93%, so the schema already documents most parameters thoroughly. The description adds minimal value beyond the schema - it mentions the control image purpose but doesn't explain parameter relationships or provide additional context that isn't already in the parameter descriptions. With high schema coverage, a baseline of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Trigger a new image generation in ControlNet mode' with the control image guiding generation. It specifies the resource (image generation) and verb (trigger), and distinguishes it from other image generation tools by mentioning ControlNet mode. However, it doesn't explicitly differentiate from sibling ControlNet tools like 'post-controlnet-img2img-inferences' or 'post-controlnet-inpaint-inferences'.

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

Usage Guidelines2/5

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

The description provides minimal usage guidance. It mentions that the control image 'can be a pose, canny map, or similar' which gives some context about when to use ControlNet, but doesn't specify when to choose this tool over other ControlNet variants (img2img, inpaint, etc.) or over regular image generation tools. No explicit alternatives, prerequisites, or exclusions are provided.

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/pasie15/scenario.com-mcp-server'

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