Skip to main content
Glama
Sign In
headlo-mcp

headlo-mcp

Official
by headlohq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_collection

Update the label or schema of a collection by specifying its ID, new label, and field definitions.

Instructions

Update a collection label or schema

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": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
schemaNo
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states that the tool updates, but doesn't mention validation, side effects, reversibility, permissions, or whether partial updates are allowed. The word 'update' is implicit in the tool name.

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 sentence, front-loaded with the action and resource, and contains no filler or redundancy. Conciseness is excellent, though it sacrifices completeness.

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 tool's complexity (3 parameters, nested schema object, no output schema, no annotations), the one-line description is inadequate. It doesn't explain how to structure the schema update, what validation rules apply, or what response to expect.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'label' and 'schema' but doesn't explain the required collection_id parameter or the structure of the nested schema object. This adds minimal meaning beyond the schema's field names.

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 uses a specific verb ('Update') and resource ('collection'), and clarifies the scope ('label or schema'), which distinguishes it from sibling tools like update_record, update_page, and create_collection.

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 vs alternatives such as update_record or create_collection. There are no prerequisites, exclusions, or context beyond the verb and resource.

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