Skip to main content
Glama

List my Hostilo sites

list_sites
Read-onlyIdempotent

Lists websites in the connected Hostilo account (newest first) with their live URLs, custom domains and last update time, including sites other people shared with this account (role: owner, editor or viewer; a viewer can only read). Call this first to find a site. Returns up to limit sites (default and max 100); if has_more is true, call again with cursor = next_cursor to get the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sites to return (1-100).
cursorNoOpaque next_cursor from the previous list_sites response. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses ordering (newest first), that sites shared with the account are included, the role model (owner/editor/viewer, with viewers read-only), and the full pagination contract with default and maximum limits plus the cursor loop. That is substantive behavioral context an agent could not get from the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler, with the identity and scope front-loaded and pagination left for the end where it belongs. The role parenthetical is dense but carries information an agent needs to interpret viewer-level results.

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

Completeness5/5

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

Covers what is returned (URLs, domains, update time), the sharing/role model, and pagination mechanics, which is everything needed to invoke and loop this tool correctly even though no output schema exists. Nothing material is left to guesswork.

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 is already 100%, so the baseline is a 3, but the description adds meaning the schema cannot: it explains the pagination loop end to end, naming the response fields has_more and next_cursor that the cursor parameter must be fed from. Without an output schema, that is a real addition rather than a restatement.

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?

States a specific verb and resource ('Lists websites in the connected Hostilo account') and adds scope details that separate it from siblings: newest-first ordering, inclusion of sites shared by others, and the fields shown (live URLs, custom domains, last update time). An agent can tell this apart from get_site or create_site without inspecting any schema.

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?

'Call this first to find a site' gives an explicit entry-point instruction for the workflow, which is the key routing signal among these siblings. It does not name specific alternatives such as get_site for single-site lookup, so the when-not guidance is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.