headlo-mcp

Official

Overview Schema Source Related Servers Discussions Admin

list_records

List records from a Headlo collection, including drafts. Use status, limit, offset, and workspace parameters to control the result set.

Instructions

List records in a collection (includes drafts)

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": {
      "collection_id": "<collection_id>"
    },
    "name": "list_records"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`status`	No
`workspace_id`	No	Workspace ID — omit to use the first workspace from context
`collection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 6, 2026

TDQS

C2.9/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 adds that drafts are included, but does not mention that the operation is read-only, default pagination behavior, or how results are ordered, which are critical for an agent to understand the tool's 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?

The description is a concise single sentence with no redundant words, front-loaded with the verb 'List'. It efficiently communicates the core purpose without unnecessary detail.

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?

Given the 5 parameters (1 required) and no output schema, the description is too sparse. It fails to explain pagination, filtering, or how to specify the collection, leaving the agent to infer critical usage details from the schema alone.

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

Parameters1/5

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

Schema description coverage is only 20%, and the tool description does not explain any parameters such as collection_id, limit, offset, or status. The only hint, 'includes drafts', is not tied to the status parameter and does not compensate for the lack of parameter 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 clearly states the tool lists records in a collection and highlights that drafts are included. This distinguishes it from get_record, which fetches a single record, and other list tools for different entities.

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 provides no guidance on when to use this tool versus alternatives like get_record or similar list tools. It does not mention any prerequisites, exclusions, or specific use cases beyond the basic listing action.

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