Skip to main content
Glama

story_get_export

Read-onlyIdempotent

Status of the latest assembled video of an episode: none, assembling, done (with a download url) or error. Free. The url expires after a while; read again for a fresh one.

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": {
      "project_id": "<project_id>",
      "episode_id": "<episode_id>"
    },
    "name": "story_get_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
episode_idYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new operational context: the call is free, the download url expires, and re-reading yields a fresh url. That is real behavioral value beyond the structured fields.

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 tight sentences: the core purpose and state enumeration come first, followed by the cost and url-expiry caveat. No filler or restatement of the tool name.

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 small polling tool with no output schema, the description covers the return states, the costly/cheap aspect, and the url lifetime. The main omission is that it never links the polling flow to the sibling that starts the export, but nothing needed to invoke the call correctly is missing.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions project_id or episode_id, so it contributes nothing about the two required parameters. The names are largely self-explanatory UUIDs, which keeps this from being a 1, but for a 0%-coverage schema the description should have identified which episode is being polled.

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?

States a specific verb and resource: retrieve the status of the latest assembled video for an episode, and enumerates every possible state (none, assembling, done with url, error). An agent can distinguish this polling tool from story_export_episode, which presumably triggers the assembly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it is a status reader you poll, and 'read again for a fresh one' hints at repeat invocation. There is no explicit statement that it should be called after story_export_episode, nor any when-not guidance against alternatives such as story_get_job.

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