Skip to main content
Glama

videogenie_job_get

Retrieve a project-owned job, its attempts, and the SQLite JSON artifact with its SHA-256 hash to resume or verify durable video job state.

Instructions

Read a project-owned job, attempts and the SQLite JSON artifact with its SHA-256.

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>",
      "job_id": "<job_id>"
    },
    "name": "videogenie_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
project_idYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successYes
project_idNo
request_idNo
storyline_idNo
schema_versionNo1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden: it does signal read-only semantics ('Read'), an ownership/authorization scoping constraint ('project-owned'), and what the response includes (attempts, artifact, SHA-256). It omits error behavior, whether the job must be in a terminal state, and whether the artifact retrieval is expensive or paginated.

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

Conciseness4/5

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

One dense sentence with the verb and scope front-loaded and no filler. It is terse to the point of being slightly compressed ('the SQLite JSON artifact with its SHA-256'), but every clause conveys information.

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?

An output schema exists, so return values need not be spelled out, and the description's recap of the artifact is a bonus. For a two-parameter read tool it is mostly adequate, but the absence of parameter detail and usage routing leaves real gaps.

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 two required parameters, so the description must compensate and largely does not: it implies project_id via 'project-owned' but never explains the identifier format, whether job_id is global or project-scoped, or how the two relate.

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?

States a specific verb and resource ('Read a project-owned job') and enumerates the payload: attempts plus the SQLite JSON artifact with its SHA-256. That is far more concrete than the sibling mutation tools (resume, archive, rename), though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the most plausible alternative, videogenie_job_resume, or of project_get for project-level data. 'project-owned' hints at an access precondition but not at selection criteria.

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