Skip to main content
Glama
Sign In
headlo-mcp

headlo-mcp

Official
by headlohq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_page_modules

Retrieve all modules and their records for a given page using the page ID. Supports public and anonymous key authentication.

Instructions

List all modules on a page with their records (public, anon key auth)

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": {
      "page_id": "<page_id>"
    },
    "name": "list_page_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the public anon key auth requirement and indicates that records are included in the result ('with their records'), which adds behavioral context beyond the tool name. However, it does not describe return shape or pagination behavior.

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: verb, resource, and scope appear immediately, with the auth context appended in a parenthetical. No unnecessary words or repetition.

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?

The tool is simple (one parameter, no output schema), and the description covers core purpose and auth context. However, it lacks explicit guidance on how this differs from list_modules_editor, leaves page_id format ambiguous, and does not clarify how records are represented in the response.

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 only parameter, page_id, has 0% schema description coverage. The description merely reuses the word 'page' ('on a page') and does not explain the expected format, type, or how the value maps to a page resource beyond the property name, leaving the agent to guess.

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 verb ('List') and resource ('modules on a page') and adds a distinctive detail ('with their records'), making it easy to distinguish from get_module (single item) and list_modules_editor (editor 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?

The parenthetical 'public, anon key auth' provides clear context for when this tool should be used (public/anonymous access), but it does not explicitly contrast with the sibling list_modules_editor or state 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.

Deploy Server

Other Tools