mixpost-mcp-server

mixpost_add_post_to_queue

Add a post to the publishing queue using its UUID, scheduling social media posts for future publication and organizing your content pipeline.

Instructions

Add a post to the publishing queue

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": {
      "postUuid": "<postUuid>"
    },
    "name": "mixpost_add_post_to_queue"
  }
}

Input Schema

Name	Required	Description	Default
`postUuid`	Yes	The UUID of the post to add to queue

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It indicates a write operation ('Add') but gives no information about side effects, permission requirements, idempotency, or consequences for the post. This is insufficient 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.

Conciseness5/5

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

The description is a single, direct sentence that is free of filler and immediately communicates the core purpose.

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?

The tool is simple with one fully documented parameter, yet the description lacks context about prerequisites (e.g., post must exist, not already queued) and effects (e.g., status change). The absence of annotations and output schema increases the need for behavioral context, leaving the description marginally adequate.

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 schema already fully documents the single parameter postUuid with its own description (100% coverage). The tool description adds no additional meaning beyond restating the action, so the baseline 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 ('Add') and resource ('post to the publishing queue'), clearly stating the tool's function. It does not explicitly differentiate from siblings like mixpost_schedule_post, but the phrase 'publishing queue' implies a distinct destination.

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?

The description provides no guidance on when to use this tool versus alternatives such as mixpost_schedule_post or mixpost_approve_post. There is no mention of prerequisites, exclusions, or preferred scenarios.

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