Skip to main content
Glama

Update a category

update_category
Destructive

Update a category. Update 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": "update_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCategory name
slugNoCategory slug
localeNoCategory locale
positionNoCategory position in the portal list to sort
category_idYesThe ID of the category
descriptionNoCategory description
portal_slugYesThe slug of the portal, as it appears in its help center link
parent_category_idNoTo define parent category, e.g product documentation has multiple level features in sales category or in engineering category.
associated_category_idNoTo associate similar categories to each other, e.g same category of product documentation in different languages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds only the help_center feature requirement; it never explains what the destruction risk means here (e.g. whether omitted fields are cleared or left untouched) or what permissions are needed beyond the feature flag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but wasteful: the first sentence and the opening clause of the second say the same thing. The one piece of genuinely new information, the feature requirement, is buried at the end after the redundancy.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with nine parameters and no output schema, the description should clarify partial-update behavior and the consequences of the destructive hint. It instead covers only the feature gate, leaving the agent to infer everything about how the update behaves.

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 100%, so all nine parameters including the nested-meaning cases (parent_category_id, associated_category_id, position) are already documented in the schema. The description adds no semantics of its own, so the baseline of 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 states a specific verb and resource (update a category) and scopes it to a portal category, which distinguishes it from account-level siblings like add_new_category_to_account. It stops short of differentiating from other update_* tools, and the second sentence largely restates the first.

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?

The only guidance offered is a feature prerequisite (help_center), which is useful eligibility information but not usage guidance. Nothing says when to update versus delete_category or how this relates to other update tools, and there is no mention of which fields should be supplied in which situation.

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