Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_getProjectContainersV1

Retrieve detailed container information for a Docker Compose project, including status, port mappings, and configuration. Monitor service health and runtime state on virtual machines.

Instructions

Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine.

This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration.

Use this to monitor the health and state of all services within your Docker Compose project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesDocker Compose project name using alphanumeric characters, dashes, and underscores only
virtualMachineIdYesVirtual Machine ID

Implementation Reference

  • Schema definition for the VPS_getProjectContainersV1 tool in the APITools interface, specifying input parameters (virtualMachineId: number, projectName: string) and generic response.
    "VPS_getProjectContainersV1": {
      params: {
        /**
         * Virtual Machine ID
         */
        virtualMachineId: number;
        /**
         * Docker Compose project name using alphanumeric characters, dashes, and underscores only
         */
        projectName: string;
      };
      response: any; // Response structure will depend on the API
    };
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns detailed information (status, port mappings, runtime configuration), which is useful behavioral context. However, it lacks details on permissions required, rate limits, error conditions, or pagination, leaving gaps for a read operation.

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 front-loaded with the core purpose in the first sentence, followed by additional context in two more sentences. Each sentence adds value (details returned, usage context) with zero waste, making it appropriately sized and well-structured.

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

Completeness3/5

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

Given no annotations and no output schema, the description provides good purpose and usage context but lacks details on return format, error handling, or behavioral constraints. For a read tool with 2 parameters, it's adequate but has clear gaps in completeness, especially without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters (projectName and virtualMachineId). The description does not add any parameter-specific details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Retrieves a list'), the resource ('all containers belonging to a specific Docker Compose project'), and the context ('on the virtual machine'). It distinguishes from siblings like VPS_getProjectListV1 (lists projects) and VPS_getProjectContentsV1 (likely different content), making the purpose specific and well-differentiated.

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 provides clear context for usage ('to monitor the health and state of all services within your Docker Compose project'), which helps an agent understand when this tool is appropriate. However, it does not explicitly state when NOT to use it or name alternatives (e.g., vs. VPS_getVirtualMachineDetailsV1 for VM-level info), missing full explicit guidance.

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

Related 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/hostinger/api-mcp-server'

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