Skip to main content
Glama

Vyexa — video link to short clips

List finished clips of a job

list_clips
Read-only

Only the finished clips of a job (id, title, duration, download_url). Each download_url requires the same Bearer key; public_url opens without the key for about 6 hours.

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": "list_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesjob_id returned by create_clips.
include_subtitlesNoInclude per-clip subtitle text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds real behavioral context beyond that: download_url requires a Bearer key while public_url is unauthenticated but expires in roughly 6 hours. It still leaves unclear what happens when a job has no finished clips (empty result vs error) or how results are ordered.

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?

Two short sentences with no filler, and the key caveat about key/expiry is placed immediately after the field list. The opening is a fragment lacking a verb, and public_url is referenced but never introduced in the field list, which slightly muddies the structure.

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?

With no output schema, the description carries the burden of describing return values and does so by listing the fields plus the auth/expiry behavior of the URLs. For a simple two-parameter read tool that is nearly complete, though pagination and the unfinished-job result shape are unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so job_id and include_subtitles are already documented; the description adds no per-parameter meaning. Baseline of 3 applies since the schema does the heavy lifting.

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 names the resource (finished clips of a job) and enumerates the returned fields (id, title, duration, download_url), which is specific enough to distinguish it from create_clips and get_job. It stops short of explicitly contrasting itself with a sibling, so it falls below a 5.

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?

Premium 'only the finished clips' implies usage for polling completion after create_clips, and the schema ties job_id back to create_clips, but the description itself states no when-to-use or when-not guidance. There is no mention of the alternative of checking job status via 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