Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_getProjectContentsV1

Retrieve complete project details, including Docker Compose file contents, metadata, and deployment status, to inspect configurations, review compose files, and assess project health.

Instructions

Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status.

This endpoint provides the full configuration and state details of a specific Docker Compose project.

Use this to inspect project settings, review the compose file, or check the overall project health.

Input Schema

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

Implementation Reference

  • TypeScript type definition (schema) for the 'VPS_getProjectContentsV1' MCP tool, including JSDoc description, input parameters (virtualMachineId: number, projectName: string), and generic response type.
       * Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status. 
    
    This endpoint provides the full configuration and state details of a specific Docker Compose project. 
    
    Use this to inspect project settings, review the compose file, or check the overall project health.
       */
      "VPS_getProjectContentsV1": {
        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?

No annotations are provided, so the description carries full burden. It indicates this is a read operation ('retrieves'), which is helpful, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the project doesn't exist. The description adds value by specifying the scope of information returned but lacks operational details.

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 appropriately sized with three sentences that are front-loaded: the first states the core purpose, the second elaborates on scope, and the third provides usage context. There's minimal waste, though the second sentence could be slightly more concise by integrating with the first.

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 the tool's moderate complexity (retrieving detailed project info), no annotations, and no output schema, the description is adequate but has gaps. It covers what information is returned and usage context, but lacks details on behavioral aspects like error handling or response format. It's complete enough for basic use but could benefit from more operational transparency.

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%, with both parameters (projectName and virtualMachineId) well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, such as explaining why both are needed or their relationship. Baseline 3 is appropriate since the 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 verb ('retrieves') and resource ('complete project information'), specifying it includes docker-compose.yml contents, metadata, and deployment status. It distinguishes from siblings like VPS_getProjectListV1 (list projects) and VPS_getProjectContainersV1 (containers only) by emphasizing 'complete' information and configuration details.

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 when to use this tool: 'to inspect project settings, review the compose file, or check the overall project health.' However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings, though the context implies it's for detailed inspection rather than listing or container-specific queries.

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