Galatic.ai

List episodes

list_episodes

Read-onlyIdempotent

List every episode of one series, sorted by season, chapter, then order, all in one response. Returns { episodes }, each the full episode record (episodeId, title, status "draft", "generating", "ready", "published" or "failed", scenes and script, contentUrl once rendered). Use get_episode for one episode and save_episode to add one. Read-only; a series the caller does not own is a 404. seriesId is the flowId of the Flow Studio flow that holds the series (from list_flows).

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": {
      "seriesId": "<seriesId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "list_episodes"
  }
}

Input Schema

Name	Required	Description
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`seriesId`	Yes
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already declare read-only and non-destructive behavior, the description adds substantive context: the result is not paginated ('all in one response'), the full episode record is returned, statuses include a specific enum-like list, contentUrl appears only once rendered, and unauthorized series access yields a 404.

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?

The description is front-loaded with purpose and return behavior, then moves directly to sibling routing and ownership semantics. Every sentence adds actionable information with no redundant restatement 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?

With no output schema, the description compensates by outlining the return object 'episodes', the fields each record contains, and status values. It also provides sufficient operational context for a read-only list tool, including sorting and the 404 condition.

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?

Schema coverage is 75%, and the schema itself thoroughly documents context, llm_model, and conversation_id. The description adds important meaning for the key required parameter by explaining that seriesId is the flowId of the Flow Studio flow holding the series, which is not present in the schema.

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?

The description states a specific verb and resource ('List every episode of one series'), including sort order and that all results are returned in one response. It explicitly distinguishes itself from get_episode and save_episode, so an agent can select it without opening sibling schemas.

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?

It names the exact alternatives: get_episode for a single episode and save_episode to add one. It also states the read-only nature and that a series the caller does not own produces a 404, giving clear usage and failure context.

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

All Galatic.ai 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.