mixpost-mcp-server

mixpost_approve_post

Approve a social media post by its UUID to authorize publishing and keep content workflows on track.

Instructions

Approve a social media post

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_approve_post"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely says 'Approve a social media post' without mentioning what approving entails: state changes, reversibility, permission requirements, or downstream effects such as publication. This lack of detail is a significant gap for a workflow-related action.

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

Conciseness2/5

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

The description is a single sentence, but it is under-specified, essentially restating the tool name without adding value. It lacks the necessary context about usage and behavioral effects, making it insufficient rather than 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?

For a simple tool with one parameter and no output schema, the description is still incomplete. It omits crucial workflow context, such as when approval is appropriate and what happens to the post upon approval. The absence of annotations further compounds the incompleteness.

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 already describes postUuid with 100% coverage. The description adds no extra meaning beyond the schema, aligning with the baseline 3 for full schema coverage. No parameter-specific nuances or formats are mentioned.

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 'Approve a social media post' clearly states the action (approve) and the resource (social media post). It is distinct from all sibling tools, which include create, update, delete, schedule, and queue actions, making the approval operation'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 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 such as mixpost_update_post or mixpost_schedule_post. The description does not mention preconditions (e.g., post must be pending approval) or exclusions, leaving the agent without contextual decision-making information.

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