Skip to main content
Glama
Sign In

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

List collections

list_collections
Read-onlyIdempotent

List the site's collections (headless CMS): id, name, slug, row and field counts, public flag.

Input Schema

NameRequiredDescriptionDefault
idNoSite id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Site id.",
+  "maxLength": 256,
+  "type": "string"
+}
    • removedInput schema / properties / site_id
      Removed value: -{
-  "description": "Site id. Pass it on every call.",
-  "maxLength": 256,
-  "type": "string"
-}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful return-shape context by naming the fields returned, though it does not mention pagination, limits, or auth requirements.

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?

A single efficiently structured sentence with the resource and returned fields front-loaded. There is no filler or repetition.

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

Completeness5/5

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

For a simple read-only list tool, annotations cover the safety profile, schema covers the single parameter, and the description covers the returned fields. No output schema is present, but the description sufficiently explains what is returned.

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

Parameters3/5

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

There is one optional parameter, and schema description coverage is 100%, with the schema already saying 'Site id.' The description only implies site scoping and adds no extra syntax or format meaning beyond the schema.

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?

States a specific verb and resource: 'List the site's collections'. It enumerates the returned fields (id, name, slug, row/field counts, public flag), which clearly distinguishes it from get_collection and list_collection_rows.

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?

Usage is implied by 'List' and by the site-scoped collections resource, but there is no explicit when/when-not guidance. It also does not name alternatives such as get_collection for a single collection or list_collection_rows for rows.

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

All PageHub toolsInspect
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