Skip to main content
Glama
Hermoso

Hermoso

Official

Check whether a TikTok post finished publishing

tiktok_post_status
Read-onlyIdempotent

Check the publish status of a TikTok post that returned pending:true, using its publishId. Returns done with the public URL, failed with TikTok's reason, or still processing.

Instructions

Follow a TikTok post that post_to_tiktok sent but TikTok was still processing (it came back pending:true). Pass the publishId it returned. Answers one of three states: done (PUBLISH_COMPLETE, with the public url once TikTok’s moderation has named it; urlStatus is ready, pending, private or draft), failed (with TikTok’s reason), or still processing, which is normal for a few minutes and is NOT a failure. Never post the video again while it is processing. Free, read-only. Needs TikTok connected (Connectors > TikTok).

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": {
      "publishId": "<publishId>"
    },
    "name": "tiktok_post_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNowhich connected TikTok account the post went out on (@handle or id from list_connector_accounts) when the profile has more than one
publishIdYesthe publishId post_to_tiktok returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / account / description
      Previous value: -"which connected TikTok account the post went out on (@handle or id from list_connector_accounts) when the brand has more than one"New value: +"which connected TikTok account the post went out on (@handle or id from list_connector_accounts) when the profile has more than one"
  2. Addedv0.1.371

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, and the description reinforces this with 'Free, read-only' while adding genuinely new context: the three-state outcome model, the urlStatus value set (ready/pending/private/draft), and the authentication prerequisite (TikTok connected via Connectors). It stops short of describing polling cadence or what a 'failed' payload looks like beyond 'TikTok's reason', which is a modest gap given openWorldHint=true.

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?

Front-loaded with the triggering condition and the required input, then the outcomes, then the caution and prerequisites. Slightly dense — the parenthetical about urlStatus and moderation naming packs several ideas into one clause — but no sentence is filler.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the three result states and the sub-states of the URL. Combined with the auth prerequisite and the no-repost warning, an agent has everything needed to call this correctly and interpret the response.

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?

Schema coverage is 100%, so both parameters are already documented in the schema, including the account param's purpose of disambiguating multiple connected accounts. The description only reiterates that publishId comes from post_to_tiktok and says nothing about the account parameter, so it adds little beyond structured data. Baseline 3 is appropriate.

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 (follow/check a TikTok post's publish status) and immediately separates itself from post_to_tiktok by scoping to posts that came back pending:true. The three possible outcomes (done with URL, failed with reason, still processing) make the tool's contract unmistakable.

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-to-use: after post_to_tiktok returns pending:true, passing the returned publishId. It also gives an explicit when-NOT-to-do-something adjacent action ('Never post the video again while it is processing') and notes that a few minutes of processing is normal, which prevents the most likely agent error.

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

Deploy Server

Other Tools