Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_updateFirewallRuleV1

Modify a specific firewall rule on a virtual machine by updating protocol, port, and source details. Changes require manual sync for affected VMs.

Instructions

Update a specific firewall rule from a specified firewall.

Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.

Use this endpoint to modify existing firewall rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firewallIdYesFirewall ID
portYesPort or port range, ex: 1024:2048
protocolYesprotocol parameter
ruleIdYesFirewall Rule ID
sourceYessource parameter
source_detailYesIP range, CIDR, single IP or `any`

Implementation Reference

  • TypeScript interface definition (schema) for the 'VPS_updateFirewallRuleV1' tool in the APITools interface, detailing input parameters (firewallId, ruleId, protocol, port, source, source_detail) and generic response.
      /**
       * Update a specific firewall rule from a specified firewall.
    
    Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.
    
    Use this endpoint to modify existing firewall rules.
       */
      "VPS_updateFirewallRuleV1": {
        params: {
          /**
           * Firewall ID
           */
          firewallId: number;
          /**
           * Firewall Rule ID
           */
          ruleId: number;
          /**
           * protocol parameter
           */
          protocol: string;
          /**
           * Port or port range, ex: 1024:2048
           */
          port: string;
          /**
           * source parameter
           */
          source: string;
          /**
           * IP range, CIDR, single IP or `any`
           */
          source_detail: string;
        };
        response: any; // Response structure will depend on the API
      };
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds context beyond basic functionality by warning that 'Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.' This discloses a critical side effect (disruption to VMs) and hints at a need for manual follow-up (syncing), which is valuable for an agent to understand the tool's impact. However, it doesn't cover other potential behaviors like error conditions, permissions required, or rate limits.

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 purpose, the second adds critical behavioral context, and the third reinforces usage. There is no wasted text, and each sentence adds value, though the third sentence is somewhat redundant with the first. A slight improvement in flow could achieve a 5.

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 complexity of updating a firewall rule (a mutation operation with potential side effects), no annotations, and no output schema, the description does a good job by including the disruptive side effect. It covers the 'what' and a key 'what happens after,' but lacks details on error handling, response format, or prerequisites. For a tool with 6 required parameters and significant impact, it's mostly complete but has minor gaps.

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?

The input schema has 100% description coverage, with each parameter well-documented (e.g., 'Port or port range, ex: 1024:2048' for 'port', enums for 'protocol' and 'source'). The description adds no additional parameter semantics beyond what the schema provides, such as explaining relationships between parameters or usage examples. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('update') and resource ('firewall rule'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling VPS_updatePostInstallScriptV1 or VPS_updateProjectV1, which are also update operations but on different resources. The mention of 'firewall' helps, but more specificity about what distinguishes this update from others would be needed for a 5.

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

Usage Guidelines3/5

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

The description implies usage by stating 'Use this endpoint to modify existing firewall rules,' which suggests it's for modifications rather than creation or deletion. However, it doesn't provide explicit guidance on when to use this versus alternatives like VPS_createFirewallRuleV1 or VPS_deleteFirewallRuleV1, nor does it mention prerequisites or exclusions. This leaves some ambiguity for the agent.

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