agent-media

list_starters

Read-only

Free, read-only, generates nothing. Fourteen proven one-line starters in four show types: drama_romance (revenge, billionaire romance, werewolf/paranormal, mafia, secret identity, second chance, thriller, family betrayal), comedy_sitcom (workplace comedy, roommates sitcom), thriller_horror (haunted house horror, snowed-in survival), fantasy_scifi (palace dragon fantasy, starship sci-fi); show_type keeps only that type's starters. Each full starter also carries season_plan (show_type, season_plot, episodes; episodes 1, 3, 5 or 10 sizes it) ready for save_season_plan and its type's writing guidance. Pass the customer's words as genre (e.g. "make me a werewolf drama") to get the full starter: premise, tone, two leads, three sets, hook pattern, cliffhanger style, Ep1 first line, ready create_series and save_series_bible arguments and a checked 10-episode grid; follow its how_to_use (the starters are the story options in series_interview round 1; one yes before any spend). Without genre, or with no match, returns every starter's one-liner to offer as options.

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_starters"
  }
}

Input Schema

Name	Required	Description	Default
`genre`	No
`episodes`	No
`show_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / episodes

Added value: +{
+  "default": 10,
+  "title": "Episodes",
+  "type": "integer"
+}

addedInput schema / properties / show_type

Added value: +{
+  "default": "",
+  "title": "Show Type",
+  "type": "string"
+}

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description's 'read-only, generates nothing' largely restates that. What it adds beyond the annotations is real: it is free (no credit spend), it discloses the full payload of a matched starter (premise, tone, leads, sets, hook pattern, Ep1 first line, create_series/save_series_bible arguments, 10-episode grid) and the season_plan shape ready for save_season_plan.

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?

Front-loaded with cost and read-only status before the detail, and every clause carries information. It is still a dense semicolon-and-parenthetical chain, and 'Free, read-only, generates nothing' states the same non-mutating property three times, which costs readability.

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?

With three undocumented parameters, no output schema and a fairly involved return shape, the description still covers inputs, return contents, the empty/no-match case, downstream tool wiring (create_series, save_series_bible, save_season_plan) and the interview workflow. Nothing material for correct invocation is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the parameters and it does: genre is explained with a concrete example ('make me a werewolf drama') and its match/no-match fallback, show_type is described as a filter over the four listed types, and episodes is documented as sizing the plan to 1, 3, 5 or 10 episodes.

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?

Opens with a specific verb+resource (lists fourteen starter templates) and enumerates the four show types and their contents, so an agent knows exactly what comes back. It also implicitly separates this from siblings like get_season_options and series_interview by positioning itself as the source of round-1 story options.

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

Usage Guidelines5/5

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

Explicit branching is given: pass the customer's words as genre to get the full starter; without genre or with no match, it returns every one-liner to offer as options. It also states the workflow constraint that the starters are the options in series_interview round 1 and that one yes precedes any spend.

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

All agent-media tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?