Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger

mail_listInboundLogsV1

Fetch paginated inbound email delivery logs for a mail order, filtered by account, date range, status, sender, or recipient, sorted by time descending.

Instructions

Retrieve paginated inbound (received mail) delivery logs for the domain attached to the given mail order. Supports filtering by account, date range, status, sender, and recipient. Results are sorted by timestamp descending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoExact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
pageNoPage number
senderNoFilter log entries by sender. Accepts a full email address or a domain.
statusNoFilter log entries by status
accountNoFilter log entries by a specific email account
orderIdYesOrder resource ID
to_dateNoDate range end (RFC 3339)
per_pageNoNumber of items per page
from_dateNoDate range start (RFC 3339)
recipientNoFilter log entries by recipient. Accepts a full email address or a domain.
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions pagination and sorting but lacks details on auth requirements, rate limits, or any side effects.

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 concise sentences with front-loaded purpose and no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, description omits return format details. Adequate for a retrieval tool but could mention log fields or pagination defaults.

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 description coverage is 100%, so baseline is 3. Description summarizes filters but adds no new meaning beyond the existing parameter descriptions.

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 tool retrieves paginated inbound delivery logs for a specific domain attached to a mail order, distinguishing it from sibling tools like mail_listOutboundLogsV1.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for inbound logs via the resource name but does not explicitly compare to alternatives or specify when not to use it.

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