tiktok_publish_videoCreate a TikTok video publish job, dry-run by default, with optional live upload by setting TIKTOK_DRY_RUN=false.
Create a TikTok video publish job. Dry-run is enabled by default; live mode requires explicit TIKTOK_DRY_RUN=false.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | ||
| caption | No | ||
| post_mode | No | MEDIA_UPLOAD | |
| target_url | No | ||
| video_path | Yes | ||
| response_format | No | json |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds the dry-run behavior, which is useful context. But it does not disclose other behavioral traits like response format, error handling, or side effects beyond job creation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, each adding value: first states purpose, second gives critical behavioral note. No filler or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the complexity of 6 parameters and no output schema, the description is minimal. It fails to explain parameter usage, return values, or workflow details (e.g., what happens after job creation). The agent needs more context for proper use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description adds no information about the 6 parameters (video_path, title, caption, etc.). The agent is left with only parameter names, enums, and types, which is insufficient for correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Create a TikTok video publish job,' using a specific verb and resource. It is distinct from sibling tools like tiktok_list_videos and tiktok_publish_status, which focus on listing or status checking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides clear guidance on dry-run default and environment variable for live mode. However, it lacks explicit when-not-to-use instructions or prerequisites (e.g., requiring authentication or video file format).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.