Skip to main content
Glama

stub

by africa.stub.api
OverviewDiscussionsAdmin

Update tag

update_tag

Update an existing tag's name or colour by id. To make a new tag use create_tag, and to remove one use delete_tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTag id. Present → update that tag; omit → create a new one.
nameNoDisplay name of the tag.
colorNoHex colour for the tag (e.g. "#8a8d82"), used for display.
groupNoFree-text group the tag belongs to. On update, passing null or "" clears an existing group; omitting the key leaves it unchanged.
archivedNoWhether the tag is archived. Omit on create to default to unarchived.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior1/5

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

The description hides a significant side effect: with the optional id, the tool also creates a tag, and it doesn't disclose any cascading effects on associated entities. Annotations provide only basic read/destructive flags.

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?

The description is brief and purposeful; every sentence adds value, including the sibling-tool alternatives.

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?

The description does not mention that the operation can upsert, that all parameters are optional, or what the result/return behavior is, leaving important invocation context uncovered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although every parameter has a description, the id parameter's semantics directly contradict the tool's stated update-only purpose, and the description only mentions name and color while schema includes group and archived.

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?

The description states the action explicitly and distinguishes from create_tag/delete_tag, but it is undermined by the schema's optional id and 'omit → create' semantics, making the tool's true purpose ambiguous.

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?

It gives clear guidance to use create_tag for new tags and delete_tag for removal, but fails to clarify when the optional id path is appropriate, especially since omitting id can create a tag.

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

All stub toolsInspect
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