Skip to main content
Glama
Sign In

agent-media

by ai.agent-media.api
OverviewDiscussionsAdmin

get_latest_episodes

Read-only

Read-only, starts and charges nothing. Where is my episode: the latest started episodes in your account, across every series, newest first (limit 1 to 20). Each row: series_id, series_title, n, title, status, say (one line to post as is: the progress line while it films, the finish line once delivered), eta and eta_seconds while it films, library (the series in the customer's agent-media Library) and, once delivered, watch (the video), page (the episode on the public series page, null for a private series), cover_url (the series cover, the thumbnail to post the episode with) and next_prompt. Drafts not started are not listed. series lists every series by id and title with its own latest_episode (n and status, null before any started), past the limit too. plan: the account's balance and its $1 Episode 1 (pilot) or micro drama (series_pass) block, which says which offer the account is on; the price of an episode is on its saved script. To follow one episode while it films, use get_episode.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds real value beyond the annotations: "charges nothing" gives cost transparency that readOnlyHint does not, and "Drafts not started are not listed" discloses a filtering rule the agent could not otherwise predict. The response is also characterized, but the tail describing series and plan blocks blurs what this tool actually returns versus get_plan_balance and get_series.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping and cost statements are front-loaded well, but the return-field enumeration becomes a single run-on chain of parenthetical asides that is hard to scan. The content mostly earns its place, yet the delivery is dense and unstructured.

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?

With no output schema, the description carries the return-shape burden and does enumerate the row fields, including nullability notes (page null for a private series, eta only while filming). What is missing is a clear boundary between the episode rows and the embedded series/plan blocks.

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 0% and the schema only declares an integer with default 5, so the description's "limit 1 to 20" supplies the missing bounds. That is meaningful compensation for a parameter that would otherwise be unbounded in the agent's view.

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 latest started episodes in your account, across every series, newest first" gives a specific resource, an explicit scope (all series, newest first) and an explicit filter (started only). It is distinguishable from list_episodes and get_episode without opening any schema.

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?

Frames the use case ("Where is my episode") and explicitly routes the per-episode follow-up case to get_episode. It does not say anything about when to prefer list_episodes or list_series instead, so the alternative coverage is partial rather than complete.

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

All agent-media toolsInspect
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