Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_createFirewallRuleV1

Add new security rules to firewalls by specifying firewall ID, protocol, port range, and source details. Ensures controlled access by allowing traffic on designated ports and IP ranges.

Instructions

Create new firewall rule for a specified firewall.

By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use.

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 add new security rules to firewalls.

Input Schema

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

Implementation Reference

  • TypeScript type definition (schema) for the 'VPS_createFirewallRuleV1' tool, auto-generated from OpenAPI specification. Defines input parameters: firewallId (number), protocol (string), port (string), source (string), source_detail (string), and generic response.
    "VPS_createFirewallRuleV1": {
      params: {
        /**
         * Firewall ID
         */
        firewallId: 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 explains the default firewall behavior (drops all incoming traffic), the requirement to add accept rules, and a critical side effect: 'Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.' This provides valuable operational context beyond basic parameter documentation.

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 4 sentences that each serve a distinct purpose: stating the core function, explaining default behavior, warning about side effects, and reinforcing usage context. It's front-loaded with the main purpose and could potentially be slightly more concise by combining some information.

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?

For a mutation tool with no annotations and no output schema, the description provides good contextual completeness. It explains the tool's purpose, when to use it, important behavioral aspects, and side effects. The main gap is the lack of information about what the tool returns (success/failure indicators, rule ID, etc.), which would be helpful given the absence of an 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?

The schema description coverage is 100%, with all 5 parameters well-documented in the schema itself. The description doesn't add any additional parameter-specific information beyond what's already in the schema descriptions, so it meets the baseline of 3 for high schema coverage without adding extra value.

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 specific action ('Create new firewall rule') and target resource ('for a specified firewall'), distinguishing it from sibling tools like VPS_deleteFirewallRuleV1 (deletion) and VPS_updateFirewallRuleV1 (modification). The verb+resource combination is precise and unambiguous.

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 add new security rules to firewalls') and includes important prerequisite information ('By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use'). However, it doesn't explicitly state when NOT to use it or mention alternatives like VPS_updateFirewallRuleV1 for modifying existing rules.

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