Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create page type

create_page_type

Create a page type template with a custom-field schema, defining which fields pages of that type carry.

Instructions

Create a page type (template) with a custom-field schema. Pages of this type carry these custom fields.

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": {
      "name": "<name>",
      "slug": "<slug>"
    },
    "name": "create_page_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoLucide icon name
nameYesDisplay name
slugYesURL-safe slug, lowercase (e.g. 'post', 'case-study')
fieldsNoCustom-field schema for this page type
urlPrefixNoURL prefix (e.g. 'blog')
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: +[
      +  "name",
      +  "slug"
      +]
  2. First observedv0.73.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so most behavioral burden falls on the description. It says nothing about slug uniqueness/collision behavior, required permissions, or whether the field schema can later be changed, which are the key risks for a create operation.

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?

Two short sentences, front-loaded with the operation and its distinguishing feature. No filler, though the second sentence is thin relational context rather than actionable detail.

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?

Given the rich, well-documented input schema and the absence of an output schema, the description covers what the tool produces at a conceptual level. The gap is behavioral (collisions, immutability of the field schema), not structural.

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?

Schema description coverage is 71%, so the baseline is 3. The description mentions the custom-field schema conceptually and notes that pages of the type inherit those fields, but adds no detail on name/slug/urlPrefix/allowChildren semantics beyond what the schema already documents.

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?

Names a specific verb (Create) and resource (page type/template), and clarifies that the input includes a custom-field schema. It is distinguishable from delete_page_type and update_page_type by the verb, though it does not explicitly contrast with them.

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?

Contains no when-to-use guidance, no prerequisites, and no routing to alternatives such as create_page (which presumably needs an existing type) or update_page_type for modifying an existing type. The second sentence explains a consequence, not when to invoke the tool.

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