Skip to main content
Glama

Check a Klipa job

get_job
Read-onlyIdempotent

Returns the status of a Klipa job and, once it's finished, its download link (valid 72 hours), a preview, and details (for AI clips: the list of clips found). Waits up to about 40 seconds for the job to finish before answering.

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_idYesThe job_id returned by a Klipa tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add operational context — and it does: a ~40 second blocking wait and a 72-hour link expiry are exactly the traits an agent must plan around. The gap is what happens when the job is still running after the wait (pending result vs. error), which is left unstated.

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 sentences, front-loaded with the primary outcome and followed by the timing constraint. Every clause carries information — outputs, link lifetime, wait duration — with no filler.

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 must describe return values, and it does so concretely (status, link, preview, details, clip list). For a single-parameter polling tool the only material omission is the behavior when the job has not finished within the wait window.

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?

Only one parameter and schema coverage is 100%; the schema already explains that job_id is "returned by a Klipa tool." The description adds no format, provenance, or error semantics beyond that, so baseline 3 is right.

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 ("Returns the status of a Klipa job") and then enumerates what comes back (download link, preview, details, clip list for AI clips). An agent can distinguish this from list_jobs or cancel_job purely from the description.

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?

Implied when-to-use is strong: the tool takes a job_id "returned by a Klipa tool" and blocks up to ~40 seconds for completion, which tells the agent this is the post-submission status check. It never explicitly names an alternative or states an exclusion (e.g., when to use list_jobs instead), so it stops short of a 5.

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