Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

hosting_getNodeJSBuildLogsV1

Retrieve Node.js build logs from a specific process. Poll repeatedly to stream live output, passing the previous line count to fetch only new lines.

Instructions

Retrieve logs from a specific Node.js build process.

To stream live output while a build is running, poll this endpoint repeatedly while the build state is running, passing the previously returned lines count as from_line to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesusername parameter
domainYesDomain name
uuidYesBuild UUID
from_lineNoLine from which to start retrieving logs
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses ANSI escape sequences and polling mechanism via from_line. However, does not specify behavior when build state is not running, log retention, or rate limits. Good but incomplete.

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?

Two short, front-loaded sentences. No wasted words. First sentence states purpose, second provides usage guidance. Efficient and clear.

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?

No output schema, but description explains polling and ANSI. Does not detail return format (e.g., lines count field) or how to retrieve all logs. For a 4-param tool, fairly complete but could hint at response structure.

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?

Schema coverage 100% (baseline 3). Description adds value for from_line by explaining its use in polling context. Other parameters have minimal schema descriptions, but description does not elaborate further. Overall, adds meaningful context beyond schema.

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?

Clear verb+resource: 'Retrieve logs from a specific Node.js build process.' Distinguishes from siblings like hosting_listNodeJSBuildsV1 (lists builds) and hosting_showJsDeploymentLogs (different context).

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 describes how to stream live output by polling while build state is 'running' and using from_line parameter. Does not contrast with other log tools or explain when not to use, but the guidance is clear and actionable.

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