Skip to main content
Glama

container_list

Read-only

List Docker containers running on a daemon, with options to include stopped ones, filter by status/label, and limit results.

Instructions

List containers on the daemon (running only by default).

Pass all=True to include stopped containers. For a compose project compose_ps groups containers by service; for swarm services use service_ps (tasks may live on other nodes).

args: all - Show all containers, including stopped ones (default False: running only) since - Only show containers created after this id or name before - Only show containers created before this id or name limit - Maximum number of results filters - Filter by attributes (e.g. status, label) sparse - Skip inspect calls and return less detail ignore_removed - Ignore containers removed during listing managed_only - Only return containers created by this MCP server (filters on the docker-mcp-server.managed label); combines with any filters given returns: list - One dict per container: full inspect payloads by default (each match is inspected, like container_inspect); sparse=True skips the per-container inspect calls and returns the daemon's abridged list entries instead

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNo
limitNo
sinceNo
beforeNo
sparseNo
filtersNo
managed_onlyNo
ignore_removedNo
Behavior5/5

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

The description adds rich behavior beyond the readOnlyHint annotation: it explains default running-only behavior, how sparse affects output, the meaning of ignore_removed, and the managed_only label filter. This fully discloses the tool's behavioral traits and return semantics.

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 clear sections: basic behavior, alternative tool guidance, parameter list, and return value explanation. Every sentence adds value, and the length is justified by the complexity of the tool (8 params, multiple behaviors).

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?

With no output schema, the description thoroughly explains return values ('full inspect payloads by default' vs. 'abridged list entries' with sparse). It also covers edge cases like removed containers and managed-only filtering, making it complete for a container listing tool.

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?

The schema has zero description coverage, but the description provides a detailed 'args:' block explaining all 8 parameters, including semantics like 'since'/'before' being id/name based and 'filters' being attribute filters. This fully compensates for the schema's lack of 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?

The description uses the specific verb 'List' with a clear resource ('containers on the daemon') and explicitly notes the default running-only scope. It also distinguishes itself from sibling tools by pointing to 'compose_ps' and 'service_ps' for alternative grouping/use cases.

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?

Provides explicit usage guidance: 'Pass all=True to include stopped containers' and directs users to 'compose_ps' for compose projects and 'service_ps' for swarm services. This clearly states when to use this tool versus alternatives.

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