headlo-mcp

Official

Overview Schema Source Related Servers Discussions Admin

list_pages

Retrieve all pages associated with a site using its site ID. Provides a complete inventory of pages for any Headlo site.

Instructions

List all pages for a site

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "list_pages"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosure. It only states 'List all pages' without mentioning return format, pagination behavior, or any side effects. The read-only nature is implicit but not stated, and no other behavioral details are disclosed.

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?

The description is a single, front-loaded sentence with no unnecessary words. It communicates the core action and target resource efficiently.

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

Completeness2/5

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

With no output schema, the description should explain what the tool returns, but it does not. It also lacks information about pagination, error handling, or required site existence. While the tool is simple, the description is too minimal to be fully actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter (site_id) with 0% description coverage. The description only says 'for a site', hinting at site_id's role but not explaining its format, constraints, or meaning. This does not compensate for the lack of schema documentation.

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 'List all pages for a site' uses a specific verb and resource, clearly distinguishing it from sibling tools like list_page_modules. The scope ('for a site') is explicit and matches the required site_id parameter.

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?

Usage context is implied: use this tool when you need a list of pages for a given site. However, there is no explicit guidance on when to use alternatives or what distinguishes it from seemingly related tools like list_page_modules or get_context.

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