Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete page type

delete_page_type
Destructive

Deletes a page type only if it is not a system type and no pages still use it; move or delete dependent pages first.

Instructions

Delete a page type. Refused for system types and for a type any page still uses - move or delete those pages first.

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": "delete_page_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTypeIdYesPage type id to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "pageTypeId"
      +]
  2. First observedv0.73.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the mutating nature is known. The description adds real value with the two refusal conditions, but says nothing about permanence, whether the identifier survives in history, or what the response looks like. Useful but partial beyond what annotations carry.

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 filler, with the action front-loaded and the refusal constraints immediately after. Every clause carries information an agent needs before invoking.

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 one-parameter destructive tool with annotations and no output schema, the definition covers the failure modes that matter most. The only meaningful gap is not stating whether the deletion is permanent or recoverable.

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?

With a single required parameter at 100% schema description coverage, the schema already explains pageTypeId fully. The description restates the object being deleted but adds no syntax, format, or lookup detail about the id, so baseline 3 applies.

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 uses a specific verb plus resource ("Delete a page type"), which separates it cleanly from delete_page and the other delete_* siblings by naming a distinct object type. It stops short of explicitly contrasting itself with update_page_type or delete_page, so it lands just below the top mark.

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?

It states two concrete preconditions under which the call is refused (system types, types still used by pages) and gives the remediation ("move or delete those pages first"). That is strong when-not guidance, though it offers no alternative tool for retiring a type still in use.

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