uplika

Retry a failed post

retry_post

Destructive

Retry the targets that failed on a publish. Targets that already went out are left alone. Naver Blog caps how many posts one ID publishes; when it does, this returns 429 naver_rate_limited with retryAfterSeconds. Do not call again before that, the draft is already in Naver. Naver Blog asks which form to publish with, every post: if options.naver_blog.form is missing this returns 400 naver_form_required with forms (id, name, when). The form is the house style to use when the person has no style of their own, so read the conversation first. If they dictated the structure or you laid it out yourself, pass options.naver_blog.layout: "as-is" and the markdown goes out unchanged. Otherwise show them the forms (naver_layout with forms: "all" lays every one out side by side) and call again with the one they pick. Do not pick for them. If a Naver target stopped right after Save as draft (errorCode naver_draft_unknown), this returns 409 naver_draft_unknown and retries nothing; check list_naver_drafts and call again with force: true only if the draft is not there. If a Naver reply did not confirm in time (errorCode naver_reply_unknown), this returns 409 naver_reply_unknown and retries nothing; look at the comment on the blog first and call again with force: true only if the reply is not there. If another post with the same content and files is queued, going out, published or scheduled on the same account, this returns 409 duplicate_post with that post's postId and retries nothing; force: true sends it anyway. If nothing failed you get nothing_to_retry. Only applies to posts published through us. This replays the same payload, so read errorCode and retryable on get_post first: when retryable is false the arguments have to change and you should call publish again instead. On Naver Blog a failed target may still have left a post or a draft in the editor, so check the blog before retrying.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	A publish id (post_…), the post's own id on the channel, or a post link (the URL you would open in a browser to see it). Links work for posts written in the channel's own app too, as long as the account is connected here.
`force`	No	Retry even though a Naver target is naver_draft_unknown (pass it only after list_naver_drafts shows the draft is not there) or naver_reply_unknown (pass it only after the comment on the blog shows no such reply), or even though another post with the same content is on the same account (duplicate_post).
`workspaceId`	No	Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / force / description

Previous value: -"Retry even though a Naver target is naver_draft_unknown (pass it only after list_naver_drafts shows the draft is not there), or even though another post with the same content is on the same account (duplicate_post)."New value: +"Retry even though a Naver target is naver_draft_unknown (pass it only after list_naver_drafts shows the draft is not there) or naver_reply_unknown (pass it only after the comment on the blog shows no such reply), or even though another post with the same content is on the same account (duplicate_post)."

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / force / description

Previous value: -"Retry even though a Naver target is naver_draft_unknown. Pass it only after list_naver_drafts shows the draft is not there."New value: +"Retry even though a Naver target is naver_draft_unknown (pass it only after list_naver_drafts shows the draft is not there), or even though another post with the same content is on the same account (duplicate_post)."

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / force

Added value: +{
+  "description": "Retry even though a Naver target is naver_draft_unknown. Pass it only after list_naver_drafts shows the draft is not there.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.",
+  "type": "string"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / id / description

Previous value: -"A publish id (post_…), a channel-side id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the channel's own app too, as long as the account is connected here."New value: +"A publish id (post_…), the post's own id on the channel, or a post link (the URL you would open in a browser to see it). Links work for posts written in the channel's own app too, as long as the account is connected here."

Changed1 schema field changedAug 12, 2026

changedInput schema / properties / id / description

Previous value: -"A publish id (post_…), a Threads media id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the Threads app too, as long as the account is connected here."New value: +"A publish id (post_…), a channel-side id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the channel's own app too, as long as the account is connected here."

First observedAug 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations (destructive=true, openWorld=true) only flag risk; the description goes far beyond by enumerating concrete error codes and their meaning (429 naver_rate_limited, 400 naver_form_required, 409 naver_draft_unknown, 409 naver_reply_unknown, 409 duplicate_post, nothing_to_retry), noting that it replays the same payload, and warning that a failed Naver target may have left a post or draft in the editor. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and every subsequent sentence carries actionable branching logic rather than filler. It is dense and long, but the length is justified by the number of distinct error states; a bulleted error-code list would have made it easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description fully compensates by spelling out every return code, the retryAfterSeconds field, the prerequisite reads (get_post errorCode/retryable, list_naver_drafts, the blog comment), and the force escalation path. An agent has everything needed to call it correctly.

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% and the schema already documents id, force, and workspaceId well, so the baseline is 3. The description nonetheless adds meaning by tying force to the specific error states and their required pre-checks, and by clarifying that workspaceId should not be re-asked — reinforcing how the parameters interact with the failure flow.

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?

States a specific verb and resource with scope: 'Retry the targets that failed on a publish. Targets that already went out are left alone.' It distinguishes itself from publish, publish_now, and publish_naver_draft by framing itself as a replay of a prior publish's failures, and it explicitly routes to publish when retryable is false.

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

Usage Guidelines5/5

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

Explicit when/when-not and alternatives throughout: don't call again before retryAfterSeconds, call publish instead when retryable is false, check list_naver_drafts before force:true, check the blog comment before force:true on naver_reply_unknown, and read the conversation / show forms via naver_layout before choosing a Naver form.

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

All uplika tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?