Skip to main content
Glama

tiktok_draft_status

Read-onlyIdempotent

Check a TikTok draft upload's status by publish ID, returning its state, failure reason, and a plain-language meaning.

Instructions

Check where a video sent with tiktok_upload_draft stands, using its publishId (/v2/post/publish/status/fetch/). Returns state, fail_reason and a one-line plain meaning. Read-only.

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": {
      "publish_id": "<publish_id>"
    },
    "name": "tiktok_draft_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
publish_idYesThe publishId returned by tiktok_upload_draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered; 'Read-only' merely restates it. The description adds value beyond annotations by naming the underlying endpoint and enumerating the returned fields (state, fail_reason, plain meaning), which matters since there is no output schema.

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?

Two tightly packed sentences with zero filler; the purpose and input source are front-loaded and the return shape follows immediately.

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

Completeness4/5

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

For a single-parameter status check with no output schema, the description covers what the tool needs (the input's provenance) and what comes back (state, fail_reason, plain meaning). It could be marginally stronger by hinting at terminal vs pending states, but nothing essential is missing.

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% and the single parameter's schema description already explains that publish_id comes from tiktok_upload_draft. The description's mention of publishId and its origin duplicates the schema rather than adding format or validation detail, so the baseline 3 applies.

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 ('Check where a video ... stands') and names the exact companion tool that produced the input ('sent with tiktok_upload_draft'), so an agent can distinguish it from the upload sibling at a glance.

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

Usage Guidelines4/5

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

The description establishes clear usage context: call this after a tiktok_upload_draft to poll the resulting publishId. It does not state explicit exclusions or polling cadence, but the when-to-use condition is unambiguous.

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