Skip to main content
Glama

Check an uploaded video

clipember_get_media
Read-onlyIdempotent

Status of one of the user's own videos: uploading / uploaded (being processed) / ready / failed (with the reason), duration, size and a thumbnail link.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "clipember_get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description is free to add the real behavioral payload: the upload lifecycle states, the fact that 'failed' carries a reason, and that the response includes duration, size and a thumbnail link. What it omits is behavior for an unknown or non-owned mediaId, so it is not a top score.

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?

One sentence, front-loaded with the resource and status set, followed by the returned fields. Nothing is repeated from structured data and no words are wasted.

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?

There is no output schema, so the description carries the return-value burden and does so by listing the status states plus duration, size and thumbnail link. Only the failure path for an invalid or unowned mediaId is 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 0% for the single mediaId parameter, so the description must compensate. It adds the ownership constraint ('the user's own videos'), which is genuine meaning beyond the schema, but never explains the identifier's form (UUID) or where an agent obtains one, leaving a real gap.

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 specific resource ('one of the user's own videos') and enumerates the exact status values returned (uploading / uploaded / ready / failed), so an agent can distinguish it from clipember_list_media, which would return many videos. It stops short of naming the sibling explicitly, which keeps it out of 5 territory.

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 'Status of one of the user's own videos' implies the obvious use case (polling an upload after clipember_upload_media_from_url), but there is no explicit when-to-use statement and no exclusion pointing to clipember_list_media for enumerating videos. Usage is inferable rather than stated.

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