Skip to main content
Glama

buildx_imagetools_create

Combine multiple per-platform Docker images into a single manifest index and push it 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 discloses that it builds and pushes in one operation, which is not evident from annotations (readOnlyHint: false, destructiveHint: false). Also mentions subprocess timeout. No contradiction with 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?

Description is a few sentences followed by a parameter list. It is fairly concise and well-structured, though the parameter list could be integrated for tighter flow.

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?

Given no output schema, the description specifies the return dict format (returncode, stdout, stderr, truncated). Covers key aspects: source requirement, operation, and default timeout. Could mention error conditions.

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?

With 0% schema description coverage, the description provides a bullet list explaining each of the 9 parameters (e.g., target, sources, append, dry_run, annotations, platforms, descriptor_files, builder, timeout_seconds). Adds essential meaning beyond the schema, though some explanations (like platforms) are brief.

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?

Clearly states the tool creates a manifest list/OCI image index from per-platform tags, replacing docker manifest create and push. Distinguishes from sibling tools like buildx_build and buildx_imagetools_inspect by specifying its unique function of combining existing tags.

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 says source tags must already be pushed and that this tool only stitches them together. Provides context for when to use, but could improve by explicitly noting when not to use (e.g., for building images from source).

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

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