Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

tiktok_publish_video

Destructive

Publish a workspace-owned video file (file_id) to the connected TikTok account via the Content Posting API. Returns publish_id + final status. Note: until the TikTok app audit passes, TikTok forces SELF_ONLY (private) visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPost caption/title (max 2200 chars; hashtags allowed).
file_idYesWorkspace `files.id` of the video to publish. Must be a video/* MIME type and status='ready'.
disable_duetNoDisable duets.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
privacy_levelNoPost visibility. Must be one the creator allows (checked against creator_info). Default SELF_ONLY — the only level TikTok accepts from unaudited apps.SELF_ONLY
disable_stitchNoDisable stitches.
disable_commentNoDisable comments on the post.
channel_account_idNoConnected TikTok channel_account.id. OMIT to auto-resolve the workspace's account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, and openWorld=true, so the write/side-effect profile is covered. The description goes beyond that by disclosing the return payload (publish_id + final status) and a real behavioral constraint: TikTok forces SELF_ONLY until the app audit passes, which directly affects the effective visibility outcome.

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?

Three compact sentences with zero filler: purpose first, return contract second, and the surprising SELF_ONLY constraint last. Every sentence earns its place and nothing is redundant with the schema.

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 mutation tool with no output schema, the description supplies the return contract (publish_id + final status) and the key constraint on visibility, while annotations handle the safety profile. It is nearly complete; minor gaps remain around error/failure behavior, but nothing essential to calling the tool correctly 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 description coverage is 100%, so the schema already documents all eight parameters, including the enum values for privacy_level and the auto-resolve behavior of channel_account_id. The description reinforces that file_id is a workspace-owned video but adds no syntax or format detail beyond the schema; 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 (publish), a specific resource (a workspace-owned video file via file_id), and a specific destination (the connected TikTok account via the Content Posting API). This clearly separates it from siblings like tiktok_list_videos, tiktok_account_stats, and the other publish tools (instagram_publish_media, youtube_upload_video) without requiring the schema to be opened.

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

Usage Guidelines3/5

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

The description implies the use case (publishing a video to TikTok) and notes the preconditions on file_id, but never explicitly states when to use this versus an alternative publish tool or when not to use it. There are no exclusions or routing guidance, leaving the agent to infer context.

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

All dialogbrain toolsInspect
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