mixpost-mcp-server

mixpost_get_tag

Fetches details of a specific tag by its UUID, returning tag information from the Mixpost social media management API.

Instructions

Get details of a specific 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_get_tag"
  }
}

Input Schema

Name	Required	Description	Default
`tagUuid`	Yes	The UUID of the tag to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior itself. It only says 'Get details' without specifying what details are returned, whether the operation is read-only, or how errors (e.g., tag not found) are handled. This is a significant gap for a read operation.

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 a single concise sentence with no redundancy or filler. It is front-loaded with the key information and earns its place with zero waste.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no annotations, no output schema), the description is adequate but incomplete. It does not mention what the 'details' consist of or any error behavior, which an agent would need to know to use the tool effectively.

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 fully documents tagUuid as 'The UUID of the tag to retrieve', so the description adds no new parameter-specific meaning. Baseline 3 applies because schema coverage is 100%; the description merely reinforces that a specific tag is targeted.

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 'Get details of a specific tag' uses a specific verb ('Get') and resource ('tag'), clearly distinguishing it from list, create, update, and delete siblings. It unambiguously states the tool's action and target.

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 like mixpost_list_tags or mixpost_get_account. The description does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the parameter and sibling names.

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