Modem

Update Topic

update_topic

DestructiveIdempotent

Update a single topic (priority, lifecycle state, archived status, issue type, or keywords). Before your first call, read the skill: modem_skills({ name: "write-tools" }).

Input Schema

Name	Required	Description
`topicId`	Yes
`archived`	No	Set to true to archive the topic, false to unarchive it.
`keywords`	No	Not supported: the topic pipeline derives the keywords. Sending this field returns 400.
`priority`	No	Update the topic priority. Valid values: very_low, low, default, high, very_high.
`issueType`	No	Not supported: the topic pipeline derives the issue type. Sending this field returns 400.
`archivedReason`	No	Optional reason for archiving. Only used when archived=true.
`lifecycleState`	No	Update the topic lifecycle state. Valid values: open, in_progress, completed, dismissed. The unknown state is AI-assessed and cannot be set directly.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / topicId / anyOf

Removed value: -[
-  {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  },
-  {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  }
-]

addedInput schema / properties / topicId / format
```
Added value: +"uuid"
```

addedInput schema / properties / topicId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / topicId / type
```
Added value: +"string"
```

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / issueType / description

Previous value: -"Update the topic issue type classification. Valid values: bug_report, feature_request, complaint, praise, or null to clear."New value: +"Not supported: the topic pipeline derives the issue type. Sending this field returns 400."

changedInput schema / properties / keywords / description

Previous value: -"Replace the topic keywords/categories. Provide the full list of keywords."New value: +"Not supported: the topic pipeline derives the keywords. Sending this field returns 400."

First observedSep 10, 2026

TDQS

C2.9/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 non-read-only, so the mutation profile is covered. The description adds the skill-reading precondition, which is genuinely useful behavioral context the annotations don't carry. It does not disclose the 400-error behavior for unsupported fields or what archiving does to a topic.

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 action and followed by the prerequisite. Very little waste, though the parenthetical field list is inaccurate rather than merely redundant.

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?

No output schema exists and this is a destructive 7-parameter write, so the description should say more about required topicId, rejection behavior for unsupported fields, and the effect of archiving. The skill pointer partially compensates by routing the agent to fuller documentation.

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 86% and the schema itself flags keywords and issueType as unsupported, so the structured data does the heavy lifting. The description's field list adds nothing beyond the schema and in fact repeats the two fields that cannot be sent, so it falls to the baseline rather than above it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update a single topic') and enumerates the modifiable fields. However, two of the enumerated fields — issue type and keywords — are explicitly unsupported and return 400, so the purpose statement actively misleads an agent about what can be changed.

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?

Tells the agent to read the 'write-tools' skill before the first call, which is a useful prerequisite. But it gives no guidance on when to choose this tool over the obvious sibling bulk_update_topics, nor when a topic should be merged instead of updated.

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

All Modem tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?