Omnia Media MCP

batch_render_catalog

Batch-render product images from prompts and presets to automate merchandising catalog creation. Submit products with scene prompts to generate catalog-ready assets in parallel.

Instructions

Batch process multiple product images across a list of prompts or presets for automated merchandising catalogs.

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": {
      "items": "<items>"
    },
    "name": "batch_render_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	List of items to stage in parallel.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses almost nothing: no indication that this fans out parallel image generation (cost/latency/rate-limit implications), no partial-failure semantics, no ordering guarantees, and no note on whether results are persisted. For an expensive multi-item generative operation, this is a significant gap.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the missing behavioral detail noted elsewhere.

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 batch generative tool with no annotations and no output schema, the definition leaves the agent without return format, per-item error handling, concurrency or size limits, and cost expectations. Complexity is high and the description does not match it.

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 coverage is 100% with a single required array, so the schema already documents product_url and scene_prompt. The description adds little beyond restating the list, and its phrase 'prompts or presets' is slightly misleading since no preset field exists in the schema.

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?

States a specific verb and resource: 'batch process multiple product images' scoped to 'automated merchandising catalogs'. The word 'batch' implicitly distinguishes it from the single-item siblings (stage_product, generate_image), but the description never names or contrasts those siblings explicitly.

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?

Offers only a vague context ('automated merchandising catalogs') with no when-to-use rule, no guidance on when to call this instead of stage_product or generate_image for a single item, and no prerequisites or limits stated.

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

Deploy Server