Skip to main content
Glama

studio_ingest_result

Copies a generated media file into content-addressed storage, verifies integrity, probes video, and marks the job complete for editorial review without spending credits.

Instructions

Copy an already generated local media file into content-addressed storage, verify integrity and ffprobe video, then mark complete pending human editorial review. No generation or credit spend.

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": {
      "jobId": "<jobId>",
      "filePath": "<filePath>"
    },
    "name": "studio_ingest_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
filePathYes
externalJobIdNo
expectedSha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the copy-to-content-addressed-storage step, integrity verification, ffprobe validation, the terminal state (complete pending human editorial review), and that no credits are spent. It omits failure behavior and overwrite semantics, keeping it short of a 5.

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 dense sentence, front-loaded with the action and pipeline steps, with zero wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Behavioral flow is well covered for a mutation tool lacking annotations and an output schema, but with four undocumented parameters at 0% coverage, an agent still lacks guidance on what each input means and how they interact.

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% across four parameters, so the description must compensate, but it never mentions jobId, filePath, externalJobId, or expectedSha256. Integrity verification hints at a hash parameter, but no parameter meaning is actually conveyed.

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 chain: copy a local media file into content-addressed storage, verify integrity, ffprobe, and mark complete pending review. This clearly distinguishes it from generation-oriented siblings like studio_dispatch_job.

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?

The clause 'No generation or credit spend' implies this is the post-generation ingestion path rather than a job dispatcher, giving useful routing context. However, it never explicitly says when to use this versus alternatives or states prerequisites/exclusions.

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