mixpost-mcp-server

mixpost_update_post

Update an existing social media post, modifying its scheduled date, time, timezone, account-specific content versions, and tag associations.

Instructions

Update an existing 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>",
      "date": "<date>",
      "time": "<time>",
      "timezone": "<timezone>",
      "accounts": "<accounts>",
      "versions": "<versions>"
    },
    "name": "mixpost_update_post"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Post date in YYYY-MM-DD format
`tags`	No	Array of tag UUIDs to associate with the post
`time`	Yes	Post time in HH:MM format
`accounts`	Yes	Array of account UUIDs to post to
`postUuid`	Yes	The UUID of the post to update
`timezone`	Yes	Timezone for the post
`versions`	Yes	Array of post versions for different accounts

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?

No annotations are provided, so the description must carry the full burden. It only says 'update an existing social media post' without disclosing whether updates are destructive (e.g., replace all fields), whether partial updates are allowed, or any side effects. There is no mention of permissions, validation, or response behavior.

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 fluff. It communicates the core action and resource efficiently, earning its place without unnecessary detail.

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?

With 7 parameters, 6 required, no output schema, and no annotations, the description is too sparse. It fails to explain what happens when updating (e.g., does it replace all versions?), any dependencies like accounts must exist, or what the response indicates. The schema covers structure but not behavioral context.

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?

Schema description coverage is 100%, so the baseline is 3. The description itself adds no parameter-level meaning beyond the schema, but the schema already provides descriptions for all fields. The description does not need to compensate for missing schema info.

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 clearly states the action (update) and the resource (existing social media post), which distinguishes it from create, delete, and schedule tools. However, it does not explicitly mention any alternative tools or nuances that set it apart beyond the verb.

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?

There is no guidance on when to use this tool vs. mixpost_create_post, mixpost_schedule_post, or mixpost_approve_post. It does not mention prerequisites, typical workflow scenarios, or any conditions under which this tool should be preferred.

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