Skip to main content
Glama
Sign In
ViralScout MCP

ViralScout MCP

by TYKAIRO-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_short_script

Create a ready-to-record short-form script framework from a topic, with tone and target length options for quick video planning.

Instructions

Generate a concise ready-to-record short-form script framework for a topic.

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": {
      "topic": "<topic>"
    },
    "name": "generate_short_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNodirect
topicYes
targetSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints that the output is a 'framework' rather than finished copy, which is useful, but it says nothing about how tone or targetSeconds shape the result, whether output is deterministic, or what the response contains.

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?

A single tight sentence with the purpose front-loaded and no filler. It is efficient, though brevity here reflects under-specification rather than disciplined trimming.

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

Completeness2/5

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

For a generative tool with no output schema, no annotations, and 0% schema description coverage, one sentence is not enough. An agent cannot tell what the returned framework looks like or how the optional parameters change it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must compensate and does not. It never mentions tone, targetSeconds, or their allowed values/ranges, leaving two of three parameters with no semantic guidance beyond their names.

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 (Generate) and resource (short-form script framework for a topic), which clearly separates it from the analyze_* siblings. It is clear what the tool produces, though it never explicitly names a sibling to distinguish itself further.

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?

There is no when-to-use guidance, no prerequisite, and no mention of alternatives versus analyze_hook, generate_remix_ideas, or the other generate_* tools. The agent must infer usage 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.

Deploy Server

Other Tools