Skip to main content
Glama

Read a draft

autoshort_get_draft
Read-onlyIdempotent

Retrieves a video draft's scenes, narration, visuals, timing estimates, credit costs, and warnings so you can review it before rendering or publishing.

Instructions

Read a draft (or a submitted director video) as scenes with narration, visual, timing estimates, estimated credits and warnings. Free.

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": {
      "draftId": "<draftId>"
    },
    "name": "autoshort_get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId returned by autoshort_draft_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is known. The description adds genuinely new behavior: the call costs no credits ('Free') and it discloses the return shape (scenes with narration, visual, timing estimates, estimated credits, warnings) even though no output schema exists. It does not say what warnings mean or whether a submitted video is read-only versus still mutable.

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?

A single front-loaded sentence that names the action, the accepted inputs, the returned fields and the cost. No filler, no repetition of the title.

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 one-parameter read tool with no output schema, the description supplies the essential return contents and the cost property, which is what an agent needs to decide and to interpret results. Minor gaps remain around what 'warnings' imply and error cases (unknown draftId, not-yet-submitted draft).

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?

With a single parameter at 100% schema coverage, the schema already documents the draftId and its provenance. The description adds meaning by broadening acceptable inputs to include a submitted director video, so an agent knows a non-draft id can legitimately be passed. Beyond that it adds no format or validation detail.

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

Purpose4/5

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

Uses a specific verb (read) against a specific resource (draft) and then enumerates the payload: scenes with narration, visual, timing estimates, estimated credits and warnings. It also notes the input may be a submitted director video rather than a draft. It does not explicitly contrast with siblings such as autoshort_get_video or autoshort_render_draft, so differentiation is left implicit.

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: the sibling name autoshort_draft_video and the schema note that draftId comes from it suggest this is the follow-up read after creating a draft. 'Free' signals a cost-based reason to prefer this over paid operations. There is no explicit when-not-to-use guidance or named alternative.

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