Skip to main content
Glama

List niches and art styles

list_niches
Read-onlyIdempotent

List the available content niches, art styles, video qualities and durations that create_video accepts. Use this to pick valid niche/artStyle values. Requires the "video:read" scope. Read-only, never charges credits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing an auth requirement ("video:read" scope) and a cost guarantee ("never charges credits"), which are not in the structured fields. The read-only/idempotent/non-destructive traits are already covered by annotations, and return shape is not described but is unnecessary for a flat value list.

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?

Three short sentences, front-loaded with what is returned, then the use case, then prerequisites. No filler or repetition of the title.

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

Completeness5/5

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

For a simple, zero-argument lookup with no output schema, the description supplies everything needed: what values come back, why to call it, the required scope, and the absence of credit cost.

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 the baseline is 4 and there is nothing for the description to clarify. It instead documents the shape of the result set (four categories of allowed values), which is the useful semantic content here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("List") plus the exact resources returned (niches, art styles, video qualities, durations), and it ties the tool to create_video so the agent knows these are enumerations for that sibling. Clearly distinct from list_videos/list_series, which enumerate user content rather than allowed parameter values.

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

Usage Guidelines4/5

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

"Use this to pick valid niche/artStyle values" gives an explicit trigger for calling it. There are no meaningful alternatives or exclusions to name for a zero-parameter enumeration lookup, so the lack of a when-not clause is not a real gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources