time-messenger-mcp-server

update_channel_category

Update a channel sidebar category's metadata—display name, sorting, mute, or collapsed state—to organize channels; rename only custom categories, not managed ones.

Instructions

Update metadata of a channel sidebar category. Provide at least one of display_name, sorting, muted, collapsed. Only custom categories can be renamed; managed categories cannot be changed.

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": {
      "team_id": "<team_id>",
      "category_id": "<category_id>"
    },
    "name": "update_channel_category"
  }
}

Input Schema

Name	Required	Description
`muted`	No	Whether the category is muted.
`sorting`	No	Channel sorting mode.
`team_id`	Yes	Team ID.
`collapsed`	No	Whether the category is collapsed.
`category_id`	Yes	Category ID.
`display_name`	No	New category display name (custom categories only).

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.0Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden: it discloses partial-update semantics (at least one field required) and a hard restriction on managed categories, which is genuinely useful. It omits permissions/authorization requirements, failure behavior, and whether the change is reversible or visible to other team members.

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?

Three compact sentences, purpose first, then the argument constraint, then the precondition. No filler or redundant phrasing.

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 an unannotated mutation tool with six parameters and no output schema, the description covers purpose, required-argument shape, and the key managed-category restriction. It still leaves out error conditions and permission requirements that an agent would want before attempting the update.

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 100%, so the baseline is 3; the description slightly exceeds that by restating the at-least-one-field contract across the four optional parameters, which the schema does not express. Field meanings themselves add nothing beyond the schema.

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 and resource ('Update metadata of a channel sidebar category') and enumerates the mutable fields, so it is clearly distinguished from create/delete/reorder category siblings. It stops short of explicitly naming those siblings as alternatives.

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?

Supplies a real precondition ('Only custom categories can be renamed; managed categories cannot be changed') and a minimum-argument rule, which guides when the call will succeed. It gives no explicit routing to alternatives such as create_channel_category or reorder_channel_categories for ordering changes.

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