headlo-mcp

Official

by headlohq

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

create_page

Create a new page in a site with a specific layout. Requires site ID, URL slug, and layout ID.

Instructions

Create a new page

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>",
      "page_id": "<page_id>",
      "layout_id": "<layout_id>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Description
`title`	No
`page_id`	Yes	URL slug, e.g. "home" or "about"
`site_id`	Yes
`layout_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 6, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic create action, but does not mention side effects, permission requirements, duplicate handling, or return behavior. This is insufficient for an agent to understand the tool's impact.

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

Conciseness3/5

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

The description is a single, concise sentence with no wasted words, making it easy to parse. However, it is underspecified and lacks key context, so it is not optimally structured for an agent needing to decide on invocation. It is brief but not comprehensive.

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?

For a create tool with 4 parameters, no annotations, and no output schema, the description is too minimal. It does not explain return values, error handling, relationships to sibling tools, or any operational constraints. This leaves significant gaps in the agent's understanding.

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 only 25% description coverage (only page_id is described). The tool description adds no parameter information, failing to clarify the meaning or requirements of title, site_id, or layout_id. Since the schema coverage is low, the description should compensate, but it doesn't.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (create) and resource (page), which distinguishes it from sibling creation tools like create_site or create_record. However, it lacks scope details such as 'in a specific site' or 'with a layout', so it doesn't fully differentiate the tool's purpose from other page-related operations.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as update_page or create_site. There is no mention of prerequisites, target use cases, or exclusions. An agent must rely solely on the tool name and schema to infer appropriate usage.

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