mixpost-mcp-server

mixpost_update_tag

Update an existing tag's name and color by providing its UUID. Specify new name and hex color values to modify tag metadata.

Instructions

Update an existing tag

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": {
      "tagUuid": "<tagUuid>"
    },
    "name": "mixpost_update_tag"
  }
}

Input Schema

Name	Required	Description
`name`	No	The new name of the tag
`tagUuid`	Yes	The UUID of the tag to update
`hex_color`	No	New hex color code for the tag

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'update' implying a mutation, but does not explain effects (e.g., whether it's idempotent, what happens if the tag does not exist, or whether any related resources are affected). This lack of detail is a significant transparency gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at five words, which is efficient with no wasted words. However, it is under-specified, lacking details that would make it appropriately sized for the tool's purpose. It could benefit from mentioning the updatable fields or conditions, so it sits between minimal and adequate.

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?

Given the tool's mutation nature, lack of annotations, and no output schema, the description is too sparse. It does not mention required vs optional parameters, expected behavior, or any prerequisites. A single sentence stating 'Update an existing tag' is insufficient for an agent to fully understand the tool's context and implications.

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?

The input schema has 100% coverage with descriptions for all three parameters (name, tagUuid, hex_color), so the schema already provides the necessary semantics. The description adds no additional parameter information beyond the action itself, keeping it at the baseline for full schema coverage.

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?

The description states a specific action ('Update') and resource ('an existing tag'), clearly distinguishing it from sibling tools like create_tag, delete_tag, and list_tags. However, it does not specify which attributes can be updated, relying on the schema for that detail.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it should be used to modify tag names or colors, nor does it exclude scenarios like creating a new tag or deleting one. The description is purely a statement of the action without contextual direction.

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