mixpost-mcp-server

mixpost_create_tag

Create a new tag to categorize and organize social media posts, with optional hex color for visual identification.

Instructions

Create a new 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": {
      "name": "<name>"
    },
    "name": "mixpost_create_tag"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The name of the tag
`hex_color`	No	Hex color code for the tag (e.g., "#FF0000")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations available, the description carries the full burden of disclosing behavioral traits. It only states the action without revealing potential side effects (e.g., whether duplicate names are rejected), required permissions, or what the tool returns upon success. This is a significant 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.

Conciseness4/5

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

The description is a single brief sentence with no unnecessary words. It is front-loaded and efficient, though it may be under-specified. However, for what it attempts to convey, it is appropriately concise.

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 low complexity (2 parameters, no nested objects) and full schema coverage, the description is minimal but leaves out important context. It does not explain return values, error conditions, or any behavior beyond the creation action. For a tool with no output schema, the description should provide more guidance on what to expect.

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 provides 100% coverage for both parameters (name and hex_color) with clear descriptions. The tool description adds no parameter-level information beyond what the schema already offers, so the baseline score of 3 applies.

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 uses a specific verb and resource ('Create a new tag'), clearly distinguishing this from sibling tools like mixpost_update_tag, mixpost_delete_tag, and mixpost_list_tags. It is unambiguous and directly reflects the tool's function.

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. There is no mention of exclusions, prerequisites, or scenarios where another tag-related tool might be more appropriate. The agent must infer usage entirely from the name and context.

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