Skip to main content
Glama
megamaced

collectives-mcp

by megamaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_tag

Idempotent

Update an existing tag's name and color by providing its ID, the current values, and the new values. Both fields are required, so fetch current data first.

Instructions

Update a tag. Both name and color are always applied, so pass the existing value for whichever one you are not changing — omitting a field is not supported by the API. Read current values with list_tags first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
colorYesSix-digit hex color code, with or without "#" (e.g. "#FF0000" or "FF0000").
tagIdYesTag id from list_tags.
collectiveIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / color / description
      Previous value: -"Hex color code."New value: +"Six-digit hex color code, with or without \"#\" (e.g. \"#FF0000\" or \"FF0000\")."
  2. First observedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description reveals that both name and color are always applied (no partial updates) and that omitting a field is unsupported. These are crucial behavioral details not captured by metadata.

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 two sentences, direct and without unnecessary words. It efficiently communicates the full-update requirement and the prerequisite read step.

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

Completeness4/5

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

The description covers the essential usage caveats and prerequisite. It does not mention consequences on associated data, but for a simple tag update this is likely sufficient, especially with no output schema defined.

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?

The schema already documents color and tagId, and the description clarifies that name and color are the updated fields. However, collectiveId is not explained in either the schema or description, leaving some ambiguity, though it is likely inferable from context.

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 description clearly states the action ('Update a tag') and identifies the resource. It also clarifies the full-update behavior, making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance: pass existing values for unchanged fields and read current values with list_tags first. This tells the agent exactly how to use the tool safely.

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

Deploy Server

Other Tools