Skip to main content
Glama

buildx_imagetools_create

Create a multi-architecture image index from existing per-platform tags. Combines and pushes the manifest in one operation.

Instructions

Create a manifest list / OCI image index from existing per-platform tags.

Replaces docker manifest create + docker manifest push — builds the index and pushes it in one operation. Source tags must already be pushed; this only stitches them together.

args: target - Tag for the new manifest list (-t) sources - Source image references to combine append - Append to the existing manifest at target rather than replacing dry_run - Print the resulting manifest without pushing annotations - OCI annotations (repeatable; passed verbatim) platforms - Filter source platforms when combining descriptor_files - Files to read source descriptors from, instead of refs builder - Override the active builder timeout_seconds - Subprocess timeout (default 600s) returns: dict - {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appendNo
targetYes
builderNo
dry_runNo
sourcesYes
platformsNo
annotationsNo
timeout_secondsNo
descriptor_filesNo
Behavior4/5

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

Description explains it builds and pushes in one operation, with no destructive behavior indicated. Annotations are consistent (readOnlyHint=false, destructiveHint=false). Adds context beyond annotations by detailing the combine-and-push action.

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?

Description is concise and well-structured: purpose first, then replacement info, precondition, and parameter list. Could be slightly more polished but effectively front-loaded.

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

Completeness4/5

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

Covers purpose, preconditions, parameter meanings, and return type for a 9-param tool. Lacks details on default behavior when target exists without append, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description provides a list of all 9 parameters with brief explanations (e.g., 'Append to existing manifest', 'Print without pushing'). This fully compensates for missing schema descriptions.

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?

Description clearly states 'Create a manifest list / OCI image index from existing per-platform tags.' It uses specific verb and resource, and distinguishes from sibling tools like buildx_build by noting it replaces older manifest commands.

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

Usage Guidelines4/5

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

Explicitly states preconditions: 'Source tags must already be pushed; this only stitches them together.' Also clarifies it replaces docker manifest create + push. No explicit when-not-to-use, but context is clear.

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/L337-org/docker-mcp'

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