Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

VPS_getActionDetailsV1

Retrieve detailed information about a specific action on a virtual machine to monitor operation status and details.

Instructions

Retrieve detailed information about a specific action performed on a specified virtual machine.

Use this endpoint to monitor specific VPS operation status and details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
virtualMachineIdYesVirtual Machine ID
actionIdYesAction ID

Implementation Reference

  • src/core/tools/vps.ts:948-975 (registration)
    Schema definition and registration entry for the 'VPS_getActionDetailsV1' tool. It is defined as an OpenAPI tool with method GET, path '/api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId}', and inputSchema requiring virtualMachineId (integer) and actionId (integer).
      "name": "VPS_getActionDetailsV1",
  "description": "Retrieve detailed information about a specific action performed on a specified virtual machine.\n\nUse this endpoint to monitor specific VPS operation status and details.",
  "method": "GET",
  "path": "/api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId}",
  "inputSchema": {
    "type": "object",
    "properties": {
      "virtualMachineId": {
        "type": "integer",
        "description": "Virtual Machine ID"
      },
      "actionId": {
        "type": "integer",
        "description": "Action ID"
      }
    },
    "required": [
      "virtualMachineId",
      "actionId"
    ]
  },
  "security": [
    {
      "apiToken": []
    }
  ],
  "group": "vps"
},
  • src/core/tools/vps.js:938-965 (registration)
    JavaScript variant of the VPS_getActionDetailsV1 tool registration entry with identical configuration.
      "name": "VPS_getActionDetailsV1",
  "description": "Retrieve detailed information about a specific action performed on a specified virtual machine.\n\nUse this endpoint to monitor specific VPS operation status and details.",
  "method": "GET",
  "path": "/api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId}",
  "inputSchema": {
    "type": "object",
    "properties": {
      "virtualMachineId": {
        "type": "integer",
        "description": "Virtual Machine ID"
      },
      "actionId": {
        "type": "integer",
        "description": "Action ID"
      }
    },
    "required": [
      "virtualMachineId",
      "actionId"
    ]
  },
  "security": [
    {
      "apiToken": []
    }
  ],
  "group": "vps"
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('Retrieve', 'monitor') but does not explicitly state it is non-destructive, nor does it mention authentication requirements, rate limits, or potential side effects. For a simple retrieval tool, the description is minimally adequate but lacks depth.

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 consists of two concise sentences. The first sentence precisely describes the tool's function. The second sentence provides a usage context. No unnecessary words or repetition. Structure is front-loaded and efficient.

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?

There is no output schema, so the description should hint at the return structure. It mentions 'detailed information' and 'monitor...status and details,' which suggests the output includes status fields. However, it could be more explicit about what fields are returned (e.g., action type, status, timestamps). For a simple retrieval tool, this is acceptable but not comprehensive.

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?

Both parameters are fully described in the input schema (100% coverage), so the description adds limited value beyond stating that the action is 'performed on a specified virtual machine.' The schema already provides parameter names and types. The description does not add constraints or format details.

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: 'Retrieve detailed information about a specific action performed on a specified virtual machine.' It uses a specific verb ('Retrieve') and identifies the resource ('action details' on a VM). This distinguishes it from sibling tools like VPS_getActionsV1 (list of actions) and VPS_getVirtualMachineDetailsV1 (VM details, not action 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 explicitly states the use case: 'Use this endpoint to monitor specific VPS operation status and details.' It implies when to use this tool (when you need details of a specific action). However, it does not explicitly mention when not to use it or list alternatives, but the context is clear enough for an agent to infer.

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

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