Skip to main content
Glama

container_export

Export a container's filesystem as a tar archive to a file on the server host or retrieve the bytes in-band.

Instructions

Export a container's filesystem as a tar archive: to a file on the server host, or in band.

With dest_path the archive streams straight to disk (no byte cap), so it handles large containers — the file is written by the server's user, ~ is expanded, and an existing file is refused unless overwrite=True. Without dest_path the tar bytes are returned in band, capped at max_bytes (default 32 MiB) because MCP base64-encodes them — a fallback for when no writable host path exists (e.g. a containerized server without a bind mount).

args: id_or_name - The container id or name dest_path - Destination path on the server host; omit to return the bytes in band overwrite - Replace dest_path if it already exists (default False) max_bytes - In-band mode: abort with ValueError beyond this many bytes (default 32 MiB) returns: bytes | dict - the tar bytes (in band), or {"path": , "bytes_written": int}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dest_pathNo
max_bytesNo
overwriteNo
id_or_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description thoroughly discloses behavior: writing to disk vs returning bytes, file overwrite refusal unless overwrite=True, byte cap in in-band mode, and server-side user handling. Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted—the tool has write side effects when dest_path is used, so readOnlyHint=false is appropriate.

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?

The description is well-structured: first paragraph explains the two modes and key constraints, second paragraph lists parameters and return values. It is appropriately sized for the complexity, though slightly verbose; no extraneous information.

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?

Given the tool's moderate complexity (two modes, multiple parameters, side effects), the description covers all essential aspects: modes, parameter details, error conditions (ValueError on exceeding max_bytes), and return formats. It is complete for an agent to select and invoke correctly.

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 coverage is 0%, but the description explains all four parameters: id_or_name, dest_path, overwrite, max_bytes—including their purposes, defaults, and behaviors. It also explains the return types (bytes vs dict), adding significant meaning beyond the 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 clearly states the verb (export) and resource (container's filesystem as a tar archive), and distinguishes two modes (to file on host or in-band). This differentiates it from sibling tools like container_archive_get which handle specific paths, so the purpose is unambiguous.

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?

The description explains when to use each mode: use dest_path for large containers (streams to disk without byte cap), omit dest_path for in-band when no writable host path exists. It also covers overwrite behavior and byte cap. However, it does not explicitly compare with siblings, but the context is clear enough for the tool itself.

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