Skip to main content
Glama

batch_generate_ipadapter

Generate multiple IP-Adapter outputs in one batch from shared reference images and distinct prompts, with optional per-job parameter randomization and unique seed control.

Instructions

Submit batch IP-Adapter jobs with optional per-generation randomization.

All jobs in the batch use the SAME reference images, but each prompt creates a distinct output. Supports parameter randomization per job.

Args: prompts: List of positive prompt strings (one per job) reference_images: Shared reference images for all jobs in batch shared_params: Static parameters applied to all generations randomize: Per-generation randomization specs (overrides shared_params) deduplicate_seeds: Ensure unique seeds across batch priority: Queue priority hint

Returns: Batch metadata with batch_id, total_jobs, queued_jobs, job_ids

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": {
      "prompts": "<prompts>",
      "reference_images": "<reference_images>"
    },
    "name": "batch_generate_ipadapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptsYes
priorityNonormal
randomizeNo
keep_loadedNo
shared_paramsNo
reference_imagesYes
deduplicate_seedsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the batch shares reference images, randomization is per-job and overrides shared_params, seeds can be deduplicated, and priority is a 'queue priority hint'. It does not say whether the call returns immediately after enqueue or blocks until completion, what happens if individual jobs fail, or anything about GPU/VRAM or auth requirements for a 7-param batch submission.

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?

The summary is front-loaded before the Args/Returns blocks, and every line maps to something an agent needs. There is mild redundancy between 'optional per-generation randomization' and 'Supports parameter randomization per job', and the Returns block partially duplicates the existing output schema.

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

Completeness3/5

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

An output schema exists, so the Returns block is not strictly needed, and the Args block covers the two required params plus most optional ones. For an unannotated 7-parameter batch mutation, the definition still leaves keep_loaded undocumented and gives no indication of queueing semantics, failure handling, or when to prefer the single-image sibling, so it is adequate but not complete.

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 0%, so the description must compensate, and its Args block does explain 6 of the 7 parameters, including the important override relationship between randomize and shared_params. However, keep_loaded is never mentioned, and the union types (randomize and shared_params accept object or string) plus valid priority values are left unexplained, so the compensation is partial.

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 first sentence names a specific verb and resource ('Submit batch IP-Adapter jobs') plus the batch scope, and the second sentence adds a real distinguishing constraint ('All jobs in the batch use the SAME reference images'). It never names the single-image sibling generate_ipadapter or batch_generate, so the agent must infer the boundary from the word 'batch' alone, which keeps it below a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the shared-reference-image constraint tells an agent this tool fits only when every job reuses the same references, and 'randomize ... overrides shared_params' hints at the choice between the two params. There is no explicit when-to-use/when-not guidance and no routing to generate_ipadapter for single generations or to batch_generate for non-IP-Adapter batches.

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