PageHub

Create collection

create_collection

Create a collection. schema = [{ key, label, type, required?, default?, help?, … }]; types: text, number, boolean, date, select, image, url, email, color, richText, media, json. Source defaults to manual. Plan-gated.

Input Schema

Name	Required	Description
`id`	No	Site id.
`name`	Yes	Display name.
`slug`	Yes	Lowercase slug, [a-z][a-z0-9-]*.
`schema`	No	Field definitions (shape in the tool description).
`source`	No	{ type: 'manual' } (default) \| airtable \| csv-upload \| google-sheet \| webhook-feed \| external-db \| hospitable.
`isPublic`	No	Visitors can read rows without auth.
`description`	No	What it holds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / source / description

Previous value: -"{ type: 'manual' } (default) | airtable | csv-upload | google-sheet | webhook-feed | external-db."New value: +"{ type: 'manual' } (default) | airtable | csv-upload | google-sheet | webhook-feed | external-db | hospitable."

Changed5 schema fields changedOct 10, 2026
- addedInput schema / properties / description / description
```
Added value: +"What it holds."
```
- addedInput schema / properties / id
```
Added value: +{
+  "description": "Site id.",
+  "maxLength": 256,
+  "type": "string"
+}
```
- addedInput schema / properties / isPublic / description
```
Added value: +"Visitors can read rows without auth."
```
- addedInput schema / properties / name / description
```
Added value: +"Display name."
```
- removedInput schema / properties / site_id
```
Removed value: -{
-  "maxLength": 256,
-  "type": "string"
-}
```
First observedSep 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare a non-readonly, non-idempotent, non-destructive, open-world write. The description adds two useful behavioral facts beyond them: the plan gate and the default source of manual. It says nothing about what happens on a slug collision, whether creation is site-scoped, or what is returned, so the added context is real but thin.

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

Conciseness4/5

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

Front-loaded verb phrase followed by the highest-value detail (the field-schema format), then defaults and gating. Dense and mostly waste-free, though the trailing "…" leaves the field-definition shape deliberately open rather than fully specified.

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

Completeness4/5

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

For a 7-parameter tool with a nested object, no output schema, and full schema descriptions, the description covers the two things the schema cannot: the nested field-definition format and the source-type enum. Gaps remain around site scoping (the `id` parameter is only labeled "Site id") and the fact that slug uniqueness is likely enforced.

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

Parameters4/5

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

Schema coverage is already 100%, but the description goes beyond it by spelling out the element shape of the `schema` array ({ key, label, type, required?, default?, help? }) and enumerating all twelve field types — details the schema itself only gestures at with "items: object". It does not add anything for `id`, `slug`, `isPublic`, or `description`, which the schema already covers.

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?

Opens with a specific verb+resource ("Create a collection") and immediately explains what a collection's contents are (a field schema with typed entries), which distinguishes it from create_collection_row and list_collections in substance. It never names a sibling or explicitly contrasts with them, so differentiation is inferred rather than stated.

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?

"Plan-gated" supplies a real precondition and "Source defaults to manual" clarifies the default path, but there is no explicit when-to-use guidance versus alternatives such as import_collection_csv (for CSV-sourced collections) or update_collection_schema for later edits. Usage is implied rather than directed.

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

All PageHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?