docker-mcp-server

Overview Schema Source Related Servers Discussions Admin

image_pull

Pull a Docker image from a registry into the daemon's local store for use. Handles specific tags, all tags, or platform-specific images, with optional per-call credentials for private repositories.

Instructions

Pull an image from a registry to the daemon's local store.

Private repositories need credentials - system_login (or docker login on the host) first, or auth_config to authenticate this call alone. Use image_load for tarballs, and registry_manifest / image_registry_data to inspect a remote image without pulling it.

Security: auth_config carries registry credentials, which many MCP clients log verbatim. Prefer docker login on the host so the docker module reuses credentials cached in ~/.docker/config.json, and leave auth_config unset.

Args: tag: The image tag (ignored when all_tags=True) all_tags: Pull all tags from the repository platform: Platform in os/arch format auth_config: Per-call registry credentials under the keys username and password; overrides the cached credential for this pull only

Returns: dict | list: The pulled image's full inspect payload, or one per image if all_tags=True

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No
`all_tags`	No
`platform`	No
`repository`	Yes
`auth_config`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.6Sep 10, 2026
- addedInput schema / properties / auth_config
```
Added value: +{
+  "default": null,
+  "type": "object"
+}
```
Addedv2.0.0Jul 4, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds meaningful behavioral context: pulling writes to the local store, auth_config carries credentials that may be logged verbatim, and tag is ignored when all_tags=True. It also discloses the return shape. This goes well beyond the annotations, though it could further mention side effects like overwriting existing local tags.

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 well-structured with a lead action, a security note, an Args list, and a Returns line. Every sentence provides actionable information, and the most important alternative-routing information appears early.

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

Completeness5/5

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

For a 5-parameter tool with one required parameter and an output schema, the description covers the main action, credential handling, parameter semantics, return value, and alternative tools. Nothing essential is missing for an agent to invoke it correctly and safely.

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?

Schema description coverage is 0%, so the description carries the full burden. It explains each parameter's behavior: tag being ignored when all_tags=True, all_tags pulling all tags, platform in os/arch format, and auth_config with its credential keys and override scope. This adds substantial meaning beyond the bare schema.

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?

The description opens with a specific verb+resource: 'Pull an image from a registry to the daemon's local store.' It also distinguishes itself from siblings by explicitly naming image_load for tarballs and registry_manifest/image_registry_data for remote inspection, so an agent can select it correctly.

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

Usage Guidelines5/5

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

It clearly states when credentials are needed and offers two paths: system_login/docker login for cached credentials, or auth_config for per-call authentication. It explicitly routes to image_load for tarballs and to remote-inspection tools when pulling is not needed, providing both positive and negative usage guidance.

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

Deploy Server