Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

hosting_updatePHPOptionsV1

Update PHP configuration options such as memory limit, execution time, and upload size for a website. Specify only the options to change.

Instructions

Updates PHP options for the website (e.g. memory_limit, max_execution_time, upload_max_filesize). Only provide the options you want to change, inside the options object.

Values above the account plan limit are silently capped to that limit, so the request can succeed with a smaller applied value. Call the Get PHP details endpoint afterwards to read the applied value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name
optionsYesMap of PHP options to update, keyed by option name. Only include options you want to change.
usernameYesusername parameter
Behavior4/5

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

Discloses silent capping of values above plan limits, which is critical behavioral information. Without annotations, this adds necessary transparency about operation semantics.

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?

Three sentences, no fluff, front-loaded with purpose. Every sentence earns its place.

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?

Covers purpose, usage, and post-call action. Lacks output details, but compensated by advising a read-back call. Adequate for an update tool without output schema.

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

Parameters4/5

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

Adds examples of PHP options and reiterates to only include changed options, enhancing the schema's generic description. With 100% schema coverage, this provides useful context beyond structure.

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 it updates PHP options for a website, with specific examples (memory_limit, etc.), distinguishing it from read-only tools like getPHPDetails and other update tools.

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?

Explicitly instructs to only provide options to change and advises calling getPHPDetails to verify applied values. Slightly lacking explicit when-not-to-use guidance, but sufficient for differentiation.

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