Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Update Tag

updateTag
DestructiveIdempotent

Update a tag's name or color by ID; omit either field to keep its current value, and changes propagate to all monitors carrying that tag.

Instructions

Renames or recolors an existing tag. Pass name, color or both; whichever you omit keeps its current value. The change shows on every monitor that carries the tag. Find the ID with listTags; to add a tag use createTag.

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": {
      "tagID": "<tagID>"
    },
    "name": "updateTag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew tag name. Omit to keep the current one.
colorNoNew tag color as a hex string (e.g. "#ff0000") or CSS color name. Omit to keep the current one.
tagIDYesThe ID of the tag to update

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
tagNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses two non-obvious traits: omitted fields retain current values, and the edit propagates to every monitor carrying the tag. It stops short of noting any permission requirements or what happens to monitors that reference the old name.

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 short sentences: purpose first, then partial-update semantics, then propagation and sibling routing. No redundant or filler wording.

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

Completeness5/5

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

With an output schema present and annotations covering safety and idempotency, the description supplies exactly the remaining context an agent needs: partial-update behavior, cross-monitor side effects, and how to obtain the required tagID.

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% and the property descriptions already say "Omit to keep the current one," so the description's "Pass name, color or both" restates rather than extends the schema. Baseline 3 applies when the schema carries parameter meaning.

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

Purpose5/5

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

The opening sentence names a specific verb and resource ("Renames or recolors an existing tag") and scopes it to modification only, which cleanly separates it from createTag and deleteTag named later.

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 explicitly routes the agent: use listTags to resolve the ID and createTag to add a new one. That covers the main alternatives in this namespace, though it does not state any when-not conditions (e.g., that this cannot change which monitors carry the tag).

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