Skip to main content
Glama
Sign In

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

Update collection schema

update_collection_schema
DestructiveIdempotent

Change a collection's fields or member gates. schema replaces all fields (get_collection first). requiredPlans gates every row. To lock single rows: add a text field keyed requiredPlans, write comma-separated plan slugs on those rows; non-members get them minus memberFields, with locked: true.

Input Schema

NameRequiredDescriptionDefault
idNoSite id.
slugYesCollection slug.
schemaNoFull field list; replaces the old one.
memberFieldsNoFields hidden on locked rows.
requiredPlansNoPlan slugs whose members alone see the rows; [] clears.
requiresCustomerLoginNoSigned-in visitors only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / memberFields
      Added value: +{
+  "description": "Fields hidden on locked rows.",
+  "items": {
+    "maxLength": 64,
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / requiredPlans
      Added value: +{
+  "description": "Plan slugs whose members alone see the rows; [] clears.",
+  "items": {
+    "maxLength": 48,
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / requiresCustomerLogin
      Added value: +{
+  "description": "Signed-in visitors only.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "schema"
-]New value: +[
+  "slug"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Site id.",
+  "maxLength": 256,
+  "type": "string"
+}
    • addedInput schema / properties / schema / description
      Added value: +"Full field list; replaces the old one."
    • removedInput schema / properties / site_id
      Removed value: -{
-  "maxLength": 256,
-  "type": "string"
-}
    • addedInput schema / properties / slug / description
      Added value: +"Collection slug."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, and the description reinforces the destructive nature by stating 'schema replaces all fields'. It further discloses non-obvious behavior: gated rows return to non-members minus memberFields with locked:true. It doesn't cover permissions or rollback.

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 the core action, then prerequisites, then the gating recipe. Dense but every sentence carries semantics; the final locking sentence is terse and slightly cryptic but earns its place.

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 destructive mutation with no output schema, the description covers the key destructive consequence and the gating mechanics an agent must know. Missing only auth/permission context and confirmation behavior.

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 100%, so baseline is 3, but the description adds real meaning beyond the schema: the requiredPlans/memberFields interplay, the locked-row visibility rule, and comma-separated slug syntax for row-level gating.

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?

Specific verb+resource: 'Change a collection's fields or member gates', and it distinguishes collection-schema-level edits from the sibling update_collection_row / create_collection_row tools by scoping itself to fields and gates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call get_collection first before replacing the schema, and explains the row-locking workflow as an alternative to whole-collection gating. It does not name sibling tools directly, so it falls just short of explicit routing.

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