Skip to main content
Glama
Sign In
ShortsFlow

ShortsFlow

by ghost1412
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

generate_social_package

Writes platform-ready titles, descriptions, hashtags, and captions for YouTube Shorts, TikTok, and Instagram Reels from a topic; returns text directly without publishing.

Instructions

Write platform-ready text for a short: a title, description, hashtags and a short caption for YouTube Shorts, TikTok and Instagram Reels. It answers immediately (no job). It uses the configured AI model; if none is reachable it returns a generic template filled with the topic instead, so check the wording. It does not publish anything.

Input Schema

NameRequiredDescriptionDefault
modeNoFormat of the video, which shapes the tone of the text.FACTS
topicYesWhat the video is about, e.g. 'Why the sky is blue'. Required.
categoryNoBroad category used to pick hashtags, e.g. 'science' or 'history'.general

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / category / description
      Added value: +"Broad category used to pick hashtags, e.g. 'science' or 'history'."
    • addedInput schema / properties / mode / description
      Added value: +"Format of the video, which shapes the tone of the text."
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "FACTS",
+  "EXPLAINER",
+  "STORY",
+  "WYR",
+  "TOP_5",
+  "CHAT_STORY",
+  "HORROR",
+  "TRUE_CRIME",
+  "BIBLE",
+  "ARTICLE",
+  "UGC",
+  "EMOJI_GUESS",
+  "REDDIT",
+  "TRIVIA",
+  "QUOTE",
+  "NEWS",
+  "RIDDLE"
+]
    • changedInput schema / properties / topic / description
      Previous value: -"Topic or title of the video"New value: +"What the video is about, e.g. 'Why the sky is blue'. Required."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses synchronous execution, that the configured AI model is used, and that an unreachable model yields a generic template that should be checked. It omits cost/rate characteristics, but the key failure mode an agent must know about is stated.

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?

Four short sentences, front-loaded with the deliverable, then the synchronous behavior, the fallback, and the scope limit. Minimal waste; the fallback sentence is the only one that could be tightened.

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 three-param generation tool with no output schema, the description names the returned artifacts and the degraded-mode behavior, which is what an agent needs to call and trust the result. Missing only explicit contrast with generate_short and any note on how required topic interacts with mode.

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 mode, topic and category are already documented in the schema. The description adds no meaning about how mode or category influence the generated text, leaving it at the baseline for a fully documented schema.

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 opens with a specific verb and output set: writes title, description, hashtags and caption for YouTube Shorts, TikTok and Instagram Reels. This clearly separates it from a renderer like generate_short, though it never names that sibling, so the distinction is inferred rather than stated.

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 line 'It does not publish anything' and 'answers immediately (no job)' implicitly scope usage against async/publishing siblings, but there is no explicit when-to-use or when-not guidance and no alternative is named. An agent must infer routing from the sibling list.

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