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

TableJSON 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.
`isPublic`	No	Visitors can read rows without auth.
`description`	No	What it holds.

Schema Changelog

Changes observed during successful MCP inspections.

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

B3.3/5.0

Behavior3/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds real context — 'Plan-gated' signals a permission/plan prerequisite. It does not disclose failure behavior (e.g., slug collision) or what a successful creation returns.

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 with purpose, then dense supporting detail in two compact sentences with no filler. The nested-field shape and type list earn their place, though the terse enumeration style borders on cryptic.

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?

No output schema and no return-value description, so an agent must infer that a collection is returned. The nested `schema` object is well covered, but slug-uniqueness/error behavior and post-creation lifecycle are omitted for a nested-object creation tool.

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?

Top-level schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it specifies the shape of each item in the `schema` array (key, label, type, required, default, help) and enumerates the allowed field types, none of which the schema supplies since items are an untyped object.

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?

Clear specific verb+resource ('Create a collection'), which an agent can distinguish from row-level siblings like create_collection_row. However it never names or differentiates against sibling tools directly, so sibling routing is left to inference.

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?

No explicit when-to-use or when-not guidance. 'Plan-gated' and 'Source defaults to manual' hint at prerequisites and a default path, but there is no statement of alternatives (e.g., update_collection_schema once a collection exists) or conditions for choosing them.

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?