Update post
auto_publish_update_postApprove, skip or edit one Auto Publish post (postId from auto_publish_list_posts). status accepts only "approved" or "skipped"; there is no reject. Approving needs a generated video and queues the post for the campaign's YouTube channel at its next publishing slot; use publish_post_now to post at once. edits may change script, title, description, videoPrompt, topic, hook, or the voice (voiceId with voiceProvider and voiceName); a cloned voice must be the user's own. Refused (409) while the post is generating. Returns { 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": {
"postId": "<postId>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "auto_publish_update_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| edits | No | Any of script, title, description, videoPrompt, topic, hook, voiceId, voiceProvider, voiceName. | |
| postId | Yes | postId from auto_publish_list_posts. | |
| status | No | "approved" or "skipped". Omit to only apply edits. | |
| context | Yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess. | |
| conversation_id | No | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request. |