Skip to main content
Glama
Taisly

Taisly

Official
by taisly

Create Taisly Post

taisly_posts_create

Publish or schedule a video post to connected social platforms after user confirmation. Use the returned historyId with the status tool to verify per-platform publishing success.

Instructions

Start publishing or schedule a video post after explicit user confirmation. success: true means Taisly accepted the request, not that every platform published it. For an immediate post, use the returned historyId with taisly_posts_status and report success only when the per-platform status is SUCCESS.

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": {
      "video": "<video>",
      "platforms": "<platforms>",
      "description": "<description>",
      "confirmed": "<confirmed>"
    },
    "name": "taisly_posts_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYesLocal video path available to the agent.
settingsNoOptional per-platform posting settings. All fields are optional; omitted values keep the existing posting behavior. These settings apply to every selected account on the corresponding platform.
confirmedYesMust be true only after explicit user confirmation.
platformsYesDestination platform IDs from taisly_platforms_list.
scheduledNoOptional ISO datetime or Unix timestamp in milliseconds.
descriptionYesPost caption or description.
previewTimeNoOptional preview timestamp used by the Taisly posting API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.10
    • addedInput schema / properties / settings
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Optional per-platform posting settings. All fields are optional; omitted values keep the existing posting behavior. These settings apply to every selected account on the corresponding platform.",
      +  "properties": {
      +    "TikTok": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "brand_content_toggle": {
      +          "description": "true discloses a paid partnership promoting a third-party business. Cannot be combined with status SELF_ONLY.",
      +          "type": "boolean"
      +        },
      +        "brand_organic_toggle": {
      +          "description": "true discloses promotion of the creator's own business. May be combined with brand_content_toggle.",
      +          "type": "boolean"
      +        },
      +        "comment_disabled": {
      +          "description": "true disables comments; false does not override the creator's account restrictions.",
      +          "type": "boolean"
      +        },
      +        "duet_disabled": {
      +          "description": "true disables Duet; false does not override the creator's account restrictions.",
      +          "type": "boolean"
      +        },
      +        "is_aigc": {
      +          "description": "Whether this video is AI-generated. Omit to keep the existing behavior.",
      +          "type": "boolean"
      +        },
      +        "status": {
      +          "description": "TikTok visibility. Choose a value permitted by the creator's account. Branded content cannot use SELF_ONLY.",
      +          "enum": [
      +            "PUBLIC_TO_EVERYONE",
      +            "MUTUAL_FOLLOW_FRIENDS",
      +            "FOLLOWER_OF_CREATOR",
      +            "SELF_ONLY"
      +          ],
      +          "type": "string"
      +        },
      +        "stitch_disabled": {
      +          "description": "true disables Stitch; false does not override the creator's account restrictions.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "YouTube": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "status": {
      +          "description": "YouTube video visibility.",
      +          "enum": [
      +            "public",
      +            "private",
      +            "unlisted"
      +          ],
      +          "type": "string"
      +        },
      +        "title": {
      +          "description": "Optional YouTube video title, up to 100 characters. Omit to use the post caption.",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With annotations already declaring non-read-only, non-idempotent, open-world behavior, the description adds critical async semantics: 'success: true means Taisly accepted the request, not that every platform published it.' It also directs the agent to verify per-platform status via taisly_posts_status before reporting success, which is exactly the behavioral nuance an agent needs.

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 sentences, zero waste. The confirmation requirement and the success-semantics warning are front-loaded, and the follow-up instruction is stated precisely enough to act on.

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?

For a 7-parameter creation tool with nested settings and no output schema, the description covers the two non-obvious risks: user confirmation and async partial success. The remaining parameter details are fully covered by the schema, so nothing critical 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%, so the schema already documents all seven parameters including nested platform settings. The description reinforces the `confirmed` parameter by saying to call after explicit user confirmation, but it adds little semantic detail about video, platforms, scheduled, or settings beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Start publishing or schedule a video post.' It distinguishes itself from taisly_posts_status by positioning that sibling as the follow-up check, but it does not explicitly contrast with taisly_reposts_create or other creation-adjacent siblings.

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?

It gives clear usage context: call only after explicit user confirmation, and after an immediate post use the returned historyId with taisly_posts_status. It does not state when-not to use this tool or explicitly route repost creation elsewhere, so it lacks full alternative-routing guidance.

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