PostKing MCP Server

edit_post_card

Update a single carousel card within a post by its index. Modify title or body text, then optionally regenerate the card's visual asset.

Instructions

Edit a single carousel card on a post by its 1-based index. Provide title and/or body to update. Set rerender=true to regenerate the visual asset.

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": {
      "postId": "<postId>",
      "cardIndex": "<cardIndex>"
    },
    "name": "edit_post_card"
  }
}

Input Schema

Name	Required	Description
`body`	No	Card body text
`title`	No	Card title
`number`	No	Card number label
`postId`	Yes	Post ID
`rerender`	No	Regenerate visual assets after edit
`cardIndex`	Yes	1-based card index (1 = first card)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It explains the edit operation and rerender behavior, which is useful, but it does not disclose whether the edit overwrites existing content, if it is reversible, or any error conditions like out-of-range cardIndex. The mention of rerender adds value but leaves important behavioral gaps.

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 two sentences, front-loaded with the core purpose, and contains no fluff. Every clause provides useful information.

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 description is adequate for a simple edit but lacks a mention of the return value, error handling, or the fact that 'number' is also updatable. Given no output schema and no annotations, the description could be more comprehensive, though it covers the main edit workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds clarification for cardIndex ('1-based') and rerender ('regenerate the visual asset'), which goes beyond the schema. However, it omits the 'number' parameter even though it is editable, so it does not fully clarify all parameters.

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 ('Edit'), the resource ('a single carousel card on a post'), and the indexing convention ('1-based index'). This distinguishes it from sibling tools like list_post_cards or generate_post_carousel, which have different purposes.

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?

The description implies usage for updating a single card and mentions the rerender option, but it does not explicitly state when to prefer this tool over alternatives like set_post_cards or bulk editing tools. No exclusions or when-not-to-use guidance is provided.

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

Deploy Server