Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

hosting_getNodeJSBuildLogsV1

Retrieve Node.js build logs from a specific build process. Poll with previous line count to stream live output.

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
uuidYesBuild UUID
domainYesDomain name
usernameYesusername parameter
from_lineNoLine from which to start retrieving logs
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that logs may contain ANSI escape sequences and explains the polling strategy. Lacks details on authentication or error responses but is sufficient for a read-only logging tool.

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 brief paragraphs with no filler. First sentence states purpose, second provides actionable usage instructions. Every sentence adds value.

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 polling mechanism and potential ANSI codes. Lacks explanation of response format or error handling, but given the tool's simplicity (4 parameters, no output schema), it is mostly complete.

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?

Schema coverage is 100% with descriptions for each parameter. The description adds context for from_line in the polling flow but does not elaborate on required parameters beyond what schema provides. Baseline of 3 is appropriate.

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 'Retrieve logs from a specific Node.js build process' with a specific verb and resource, distinguishing it clearly from sibling tools like hosting_listNodeJSBuildsV1 or hosting_showJsDeploymentLogs.

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?

Provides explicit guidance on when to poll (while build state is running) and how to use from_line for incremental fetching. Does not explicitly exclude alternatives but offers a clear usage pattern.

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