Skip to main content
Glama
Sign In
portainer-mcp

portainer-mcp

by ginkida
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

portainer_images_list

List Docker images on a Portainer endpoint, with optional filtering by image reference to find specific images.

Instructions

List Docker images on an endpoint.

Args: endpoint_id: Target endpoint ID (uses default if omitted) reference_filter: Only return images matching this reference (e.g. 'nginx' or 'nginx:1.25'; server-side Docker filter)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "portainer_images_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpoint_idNo
reference_filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / reference_filter
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Reference Filter"
+}
  2. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses default behavior for endpoint_id and that reference_filter is a server-side Docker filter, but does not explicitly state that the operation is read-only or mention any side effects, permissions, or response details. With no annotations, the description provides moderate transparency.

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 brief and front-loaded with the main purpose. The argument list is clear but slightly verbose (e.g., 'Target endpoint ID (uses default if omitted)'). Could be more terse, but no wasted sentences.

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 the tool's simplicity and the presence of an output schema, the description covers the core purpose and parameter semantics. It lacks mention of read-only nature or authentication requirements, but these are partially implied by the action. Mostly complete for a list endpoint.

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 description coverage, the description fully explains both parameters: endpoint_id (target endpoint, defaults if omitted) and reference_filter (filter by image reference, with examples). This adds significant 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 clearly states the action ('List'), resource ('Docker images'), and scope ('on an endpoint'). It distinguishes itself from sibling tools like portainer_image_inspect (single image), portainer_image_pull (download), and portainer_image_remove (deletion).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives (e.g., portainer_image_inspect for details on one image). The description does not provide when-not-to-use or compare with sibling tools.

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

Deploy Server

Other Tools