kadenzo-mcp

update_post

Edit unpublished social posts to change content, accounts, scheduling, media, options, or thread structure before they go live.

Instructions

Edit a post that has not published yet — change content, accounts, time, media, options, or thread.

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": {
      "id": "<id>"
    },
    "name": "update_post"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`thread`	No
`content`	No
`options`	No
`media_urls`	No
`account_ids`	No
`scheduled_for`	No
`platform_content`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.2Jul 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so description must disclose behavior. It states the tool edits only unpublished posts and lists changeable aspects, but does not cover auth requirements, error conditions, or side effects. Adequate but not comprehensive.

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?

Single sentence that is front-loaded with the key condition and lists changeable fields concisely. No wasted words.

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?

The tool has 8 parameters, nested objects, and no output schema. The description does not explain return values, error conditions, or provide guidance on the complex thread parameter. Significant gaps remain for effective use.

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?

With 0% schema description coverage, the description maps several parameter names to named changeable aspects (content, accounts, time, media, options, thread) but does not explain the structure of complex parameters like thread or platform_content, or the role of the required id.

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?

Description clearly states the verb 'edit' and the resource 'post', with a specific condition 'that has not published yet', distinguishing it from sibling tools like schedule_post or cancel_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage only for unpublished posts but does not explicitly state when not to use it or mention alternative tools for published posts. The guidance is implied rather than explicit.

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

Deploy Server