Skip to main content
Glama
Taisly

Taisly

Official
by taisly

Get Platform Posting Schema

taisly_platform_schema
Read-onlyIdempotent

Retrieve posting constraints and supported settings for a social platform to validate video uploads before publishing.

Instructions

Get posting constraints and supported settings for a destination platform.

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": {
      "platform": "<platform>"
    },
    "name": "taisly_platform_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform name, for example TikTok, Instagram, YouTube, X, or Facebook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds that the result is per-destination posting constraints, but says nothing about return shape, completeness, caching, or whether unsupported platforms error versus return empty — meaningful gaps for a schema-lookup tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and the payload. Nothing is wasted, though the brevity borders on under-specification for a discovery tool whose output matters.

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?

Read-only annotations carry the safety story, but with no output schema the description is the only place an agent could learn what 'constraints and settings' actually contains. It stops short of describing the returned fields or how to consume them before creating a post.

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 'platform' parameter is documented with concrete examples (TikTok, Instagram, YouTube, X, Facebook), so the schema does the heavy lifting. The description adds no additional meaning about accepted values, case sensitivity, or error behavior for unknown platforms.

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 ('Get') and resource ('posting constraints and supported settings' for a destination platform), which is more informative than the title alone. It is distinguishable from taisly_platforms_list, but it never explicitly contrasts itself with taisly_posts_validate, which sounds adjacent in purpose.

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

Usage Guidelines2/5

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

No indication of when to call this versus taisly_platforms_list or taisly_posts_validate, and no mention of the natural workflow (e.g., call before taisly_posts_create to learn required fields). Usage must be inferred entirely from the name.

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