Skip to main content
Glama
Sign In
taisly

Taisly

Official
by taisly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Validate Taisly Post

taisly_posts_validate
Read-onlyIdempotent

Validates a local video path, target platform IDs, caption, and optional schedule before publishing to catch missing or invalid post inputs.

Instructions

Validate a local video path, destination platform IDs, caption, and optional schedule before publishing.

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.
platformsYesDestination platform IDs from taisly_platforms_list.
scheduledNoOptional ISO datetime or Unix timestamp in milliseconds.
descriptionYesPost caption or description.

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that this is a pre-publish check, which is useful workflow context, but says nothing about what a failed validation produces (errors, warnings, partial results) or whether it mutates any stored draft state.

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?

A single front-loaded sentence with the verb first and the validated surface enumerated. Nothing redundant and nothing padded.

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

Completeness3/5

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

For a 5-parameter validation tool with nested settings objects and no output schema, the description omits the most decision-relevant behavior: what the caller gets back and what to do on failure. It is adequate to identify the tool but not to predict its 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 description coverage is 100% and the nested TikTok/YouTube settings are richly documented in-schema. The description only restates the top-level field names ('video path, platform IDs, caption, schedule') without adding format, ordering, or cross-field constraints beyond what the schema already says.

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?

States a specific verb (validate) and enumerates exactly what is validated: local video path, destination platform IDs, caption, and optional schedule. The phrase 'before publishing' implicitly distinguishes it from taisly_posts_create, though the sibling is never named.

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?

'before publishing' implies the pre-flight use case, but the description never explicitly says to call this before taisly_posts_create, nor does it say whether validation is required or merely optional. The downstream alternative is left to inference.

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