Skip to main content
Glama

Delete a category

delete_category
DestructiveIdempotent

Delete a category. Deletes a category of a portal. Requires feature: help_center.

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": {
      "portal_slug": "<portal_slug>",
      "category_id": "<category_id>"
    },
    "name": "delete_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
category_idYesThe ID of the category
portal_slugYesThe slug of the portal, as it appears in its help center link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description's only added behavioral fact is the `help_center` feature prerequisite; it omits consequences such as whether articles in the category are also removed or whether deletion is recoverable.

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?

It is short and front-loaded, with the verb leading. The first sentence merely restates the title and the second largely restates the first, but the feature requirement is a non-obvious detail worth surfacing and no sentence is bloated.

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

Completeness3/5

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

For a simple two-parameter destructive operation with full schema coverage and rich annotations, the description covers the essentials. It is still thin on blast radius — an agent cannot tell from the definition what else disappears when a category is deleted.

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 coverage is 100%, with both `portal_slug` and `category_id` documented in the schema itself, so the baseline is 3. The description adds no meaning about how the slug is derived or which portals expose category IDs.

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 states a specific verb (Delete) and resource (category) and adds scope with 'of a portal.' It does not, however, distinguish this from sibling destructive tools such as delete_portal or delete_article, so an agent must infer the distinction from the name alone.

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 definition supplies one real usage constraint — the tool requires the `help_center` feature — which is genuinely useful for deciding whether a call will succeed. It offers no when-to-use/when-not guidance and does not point to update_category or add_new_category_to_account as alternatives for non-deletion goals.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources