Skip to main content
Glama

AIClipMaker.org

List a job's clips

list_clips
Read-onlyIdempotent

The clips of a completed job, with titles, platform-ready descriptions and download URLs. In MCP Apps-capable clients the result also renders as an interactive clip picker.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuine context beyond them: a completion precondition and the fact that MCP Apps-capable clients render an interactive picker rather than raw data. It does not disclose behavior for incomplete jobs (error vs. empty result) or pagination, leaving the main behavioral question unanswered.

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 filler, and the substantive content (what is returned) is front-loaded ahead of the client-specific rendering note.

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?

No output schema exists, and the description does adequately summarize the returned fields, which is the right compensation. However, for a single-parameter retrieval tool it omits where job_id comes from and what happens on an incomplete or invalid job, leaving 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% and the description never mentions job_id — no format, no hint that it comes from process_video or get_job_status. With a single required identifier that is the only input, the description should say what it is and where to obtain it, and it does not.

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?

Names a specific resource (a job's clips) and enumerates the payload the agent gets back: titles, platform-ready descriptions, download URLs. The 'completed job' qualifier also scopes which jobs it applies to. It does not explicitly contrast with siblings like get_job_status or recut_clip, so it falls short of 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?

The phrase 'of a completed job' implies a precondition (the job must be finished) and hints that this is the retrieval step after processing. It never states what to do if the job is not complete, nor names an alternative tool for other stages, so usage is only implied.

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