Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update page type

update_page_type
Destructive

Updates a page type's name, slug, icon, URL prefix, child-page rule, or custom-field schema. Omitted fields keep their values, except fields, which replaces the entire schema.

Instructions

Update a page type: name, slug, icon, url prefix, allowChildren, or its custom-field schema. Fields you omit keep their current value, EXCEPT fields, which replaces the whole 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": {
      "pageTypeId": "<pageTypeId>"
    },
    "name": "update_page_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoLucide icon name
nameNoDisplay name
slugNoURL-safe slug, lowercase
fieldsNoReplaces the whole custom-field schema. Read the current one with get_page_type first and send it back with your edit applied - fields you omit are dropped, and their values stop being editable on existing pages.
urlPrefixNoURL prefix (e.g. 'blog')
pageTypeIdYesPage type id to update
descriptionNo
allowChildrenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / definitions / __schema0 / properties / defaultValue / description
      Added value: +"Default value, always a string. Only a field that holds one string, number or boolean ever seeds from it; a structured type or a hasMany relation never does."
    • changedInput schema / definitions / __schema0 / properties / description / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "type": "string"
      +    },
      +    "propertyNames": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / definitions / __schema0 / properties / label / additionalProperties
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / definitions / __schema0 / properties / label / description
      Added value: +"The field's label per language code of the workspace: { en: 'Size', pl: 'Rozmiar' }. At least one language."
    • removedInput schema / definitions / __schema0 / properties / label / minLength
      Removed value: -1
    • addedInput schema / definitions / __schema0 / properties / label / propertyNames
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / definitions / __schema0 / properties / label / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / definitions / __schema0 / properties / maxDecimals
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "For a 'number' field: most digits after the decimal point (0 = whole numbers). null clears the rule."
      +}
    • addedInput schema / definitions / __schema0 / properties / maxItems
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Most items a list-valued field accepts (same types as minItems). null clears the rule."
      +}
    • addedInput schema / definitions / __schema0 / properties / maxSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "For a 'media' field: largest accepted asset, in bytes. null clears the rule."
      +}
    • addedInput schema / definitions / __schema0 / properties / minItems
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Fewest items a list-valued field accepts (repeater, list, multiselect, hasMany relation, media with multiple: true). Ignored on a single-value field. null clears the rule."
      +}
    • changedInput schema / definitions / __schema0 / properties / options / description
      Previous value: -"Choices for a 'select' or 'multiselect' field. Required (non-empty) for those types."New value: +"Choices for a 'select' or 'multiselect' field: [{ value: 's', label: { en: 'Small' } }]. Required (non-empty) for those types; values must be distinct."
    • addedInput schema / definitions / __schema0 / properties / options / items / properties
      Added value: +{
      +  "label": {
      +    "additionalProperties": {
      +      "type": "string"
      +    },
      +    "description": "What the editor sees, per language: { en: 'Small', pl: 'Mały' }.",
      +    "propertyNames": {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "value": {
      +    "description": "The stored value - what a record holds and filters match.",
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +}
    • addedInput schema / definitions / __schema0 / properties / options / items / required
      Added value: +[
      +  "value",
      +  "label"
      +]
    • changedInput schema / definitions / __schema0 / properties / options / items / type
      Previous value: -"string"New value: +"object"
    • addedInput schema / definitions / __schema0 / properties / validationMessage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Shown instead of the default message when any rule on this field fails. null clears it."
      +}
    • addedInput schema / required
      Added value: +[
      +  "pageTypeId"
      +]
  2. First observedv0.73.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only mutation, so the bar is lower, and the description still adds real value by disclosing the asymmetric merge behavior and singling out `fields` as a full replacement. It does not repeat the stronger consequence spelled out in the schema (dropped fields stop being editable on existing pages), but the destructive character is at least surfaced.

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?

Two sentences, zero padding, with the field list first and the critical exception front-loaded in second position. Every clause carries information an agent needs before calling.

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 an 8-parameter mutation with a deep nested custom-field schema and no output schema, the description covers the essential contract: what can change and how omission is interpreted. The one meaningful gap is that the irreversible consequence of dropping fields is only documented inside the schema, not in the description itself.

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 75%, so the baseline is 3; the description earns an extra point by stating the cross-parameter omit-keeps-current rule that the schema does not state for name, slug, icon, urlPrefix, or allowChildren. The `fields` replacement warning duplicates the schema text rather than extending it.

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?

The description names a specific verb and resource ('Update a page type') and enumerates the updatable surface: name, slug, icon, url prefix, allowChildren, and the custom-field schema. The update verb plus the sibling names create_page_type/delete_page_type/get_page_type make the role obvious, though the description never explicitly contrasts itself with those siblings.

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?

The patch semantics ('fields you omit keep their current value') implicitly tell an agent this is a partial-update tool, and the `fields` exception hints at a read-modify-write workflow. However, the explicit instruction to call get_page_type first lives only in the schema's `fields` property, not in the description, and nothing says when to prefer this over update_page_settings or update_page_layout.

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