Skip to main content
Glama

List niches, styles and durations

autoshort_list_niches
Read-onlyIdempotent

Retrieve the content niches, art styles, video qualities and durations that the video generation tools accept. Use it to check valid options before creating a short video.

Instructions

List the content niches, art styles, video qualities and durations the generation tools accept. Free.

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": "autoshort_list_niches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.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, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely new fact, that the call costs no credits ("Free"), plus the fact that results are the set of values the generation tools accept; it says nothing about return shape beyond that, which is acceptable for a fixed enumeration.

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?

Two short sentences, front-loaded with the primary purpose and ending with the cost qualifier. No filler, no restatement of the title verbatim.

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, read-only reference lookup with no output schema, the description covers the essential question of what values are returned. A brief note on whether options vary per generation model would close the remaining gap, but nothing critical is missing.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-related claims are made or needed.

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?

A concrete verb ("List") plus concrete resources ("content niches, art styles, video qualities and durations") and a scope qualifier ("the generation tools accept"). An agent knows exactly what data comes back, though nothing in the text separates it from other enumeration siblings like autoshort_list_options or autoshort_get_capabilities.

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?

"Free" signals cost but not when to call. There is no statement such as "call this before generate_video to learn valid values" and no exclusion against the other list_* siblings, so the agent must infer that this is a pre-generation lookup.

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