Skip to main content
Glama

storyshort_list_niches

Retrieve available video niches, art styles, qualities, and duration options to select valid generation settings before creating a short video.

Instructions

List available video niches, art styles, video qualities, and duration options for video generation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "storyshort_list_niches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; the leading verb "List" plus zero-parameter schema strongly imply a safe read-only lookup. It adds real value by enumerating the four categories of options returned, which is behavioral disclosure beyond the name. It does not say whether these options are static/global or account-specific, nor whether any auth is required.

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 no filler; the verb comes first and the payload categories follow immediately. Every word carries information and nothing is repeated.

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 zero-parameter, no-output-schema lookup tool, the description is nearly complete because it enumerates the returned data, which compensates for the missing output schema. The one gap is not linking those returned options to the arguments of storyshort_generate_video, which is the tool's primary downstream use.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline applies. Schema coverage is 100% by construction and the description makes clear no inputs are needed to get the full option set.

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?

Uses a specific verb ("List") with four explicitly named resource categories (niches, art styles, qualities, duration options), so an agent knows exactly what data comes back. It doesn't explicitly distinguish itself from a search/list call like storyshort_list_videos, but the "for video generation" qualifier and the enumeration make the resource boundary readable.

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 phrase "for video generation" implies this is a prerequisite lookup before storyshort_generate_video, which is useful implied guidance. However, it never states when to call this versus other list tools, nor that its returned values are the valid options to pass when generating.

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