mixpost-mcp-server

mixpost_delete_post

Delete a specific social media post by providing its UUID. Removes unwanted posts from your Mixpost accounts.

Instructions

Delete a specific 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_delete_post"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description only says 'Delete a specific post' and provides no details on destructiveness, irreversibility, permissions, or cascading effects. With no annotations provided, the description carries the full burden but fails to disclose any behavioral traits beyond the explicit action.

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 sentence, concise and front-loaded. It contains no extraneous words and effectively communicates the primary purpose.

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 lack of annotations and output schema, the description is too minimal. It does not explain whether deletion is permanent, what happens to associated media, or any prerequisites. A simple delete operation still benefits from some behavioral context, which is absent here.

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 describes the sole parameter (postUuid) with a clear description. The tool description adds no additional meaning beyond the schema, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (delete) and the resource (a specific post), distinguishing it from sibling tools like mixpost_delete_multiple_posts by emphasizing 'a specific post'. The verb is specific and the resource is 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_delete_multiple_posts. The description simply states the action without any contextual cues about selection criteria or exclusions.

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