Skip to main content
Glama

OpenShorts.io

Get a clipping job and its clips

get_job

Status and progress of a job. When done, lists every clip with title, score, reason, hook line, suggested TikTok and Instagram captions, and download links valid for one hour.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one genuinely valuable trait beyond the schema: download links are valid for only one hour, which affects downstream use. However, it omits job state values, whether completed jobs remain retrievable, error behavior for unknown job_ids, and any rate or auth considerations.

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 with no waste: the first covers status/progress, the second enumerates the completed-state payload. The most decision-relevant fact (the job may not be done yet) is front-loaded.

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?

Because there is no output schema, the description must carry return-value information — and it does so reasonably, enumerating clip fields (title, score, reason, hook, captions, links). What remains missing is the shape of the in-progress response, the set of possible statuses, and how the caller obtains a valid job_id.

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% for the single required parameter, job_id, so the schema adds no meaning at all. The description never mentions job_id, where it comes from, or its format — presumably it is returned by clip_video or list_jobs, but the agent must infer that.

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?

The description states a specific resource and scope: the status and progress of a single job, plus its clips once complete. That is clearly distinguishable from list_jobs (multiple jobs), though the description never explicitly names the sibling or says 'single job by ID'.

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?

The description gives a clear context cue in 'When done, lists every clip...', which tells the agent this is the polling/retrieval step for tracking a job's progress. It stops short of explicitly stating when to prefer it over list_jobs or get_usage, and offers no guidance on how often to poll.

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