Loading ToolBench
MCP server for Hostinger API providing tools for hosting management, WordPress deployment, JavaScript application deployment, billing operations, and domain management
Server defines 14 tools with explicit schemas and descriptions. Naming follows verb_noun pattern (hosting_*, billing_*) but lacks clarity in distinguishing similar operations. Descriptions are present (avg ~180 chars) but many lack actionable context for LLM selection. Schemas are well-formed with typed properties, but output schemas are entirely undocumented. Critical gaps: no error handling guidance, no parameter constraints (enums), no pagination documentation despite list tools, and no security/permission declarations.
Cancel a subscription and stop any further billing. Use this endpoint when users want to terminate active services.
Create a new service order. DEPRECATED: To purchase a domain, use POST /api/domains/v1/portfolio instead. To purchase a VPS, use POST /api/vps/v1/virtual-machines instead. To place order, you need to provide payment method ID and list of price items from the catalog endpoint together with quantity. Coupons also can be provided during order creation. Orders created using this endpoint will be set for automatic renewal. Some `credit_card` payments might need additional verification, rendering purchase unprocessed. We recommend use other payment methods than `credit_card` if you encounter this issue.
Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts.
Retrieve catalog items available for order. Prices in catalog items is displayed as cents (without floating point), e.g: float `17.99` is displayed as integer `1799`. Use this endpoint to view available services and pricing before placing orders.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields without knowing response structure. All 14 tools lack return type documentation.
Billing tool descriptions are generic and lack context for LLM selection. 'Set the default payment method' (50 chars) does not explain when to use vs alternatives, prerequisites, or side effects. Descriptions should be 50-200 chars with actionable context.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
Retrieve available payment methods that can be used for placing new orders. If you want to add new payment method, please use hPanel. Use this endpoint to view available payment options before creating orders.
Retrieve a list of all subscriptions associated with your account. Use this endpoint to monitor active services and billing status.
Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders.
Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The archive will be extracted and deployed directly without any build steps. The username will be automatically resolved from the domain.
Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.
Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment.
Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain.
List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.
Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. E.g., 'domain not found' or 'insufficient permissions' have no recovery hints.
No parameter constraints (enums, ranges, patterns). E.g., 'states' in hosting_listJsDeployments declares enum values in schema but descriptions lack format guidance. 'domain' parameter accepts any string with no validation hint.
Destructive operations (billing_deletePaymentMethodV1, billing_cancelSubscriptionV1) lack confirmation or dry-run support. No guidance on whether these are idempotent or what happens on retry.