Skip to main content
Glama

Get clip

get_clip
Read-only

Retrieve catalogue metadata for a single verified clip using its clip ID, so you can inspect details before selecting or accessing the clip file.

Instructions

Return catalogue metadata for one verified clip.

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": {
      "clip_id": "<clip_id>"
    },
    "name": "get_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes

Output Schema

NameRequiredDescriptionDefault
clipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the returned payload is catalogue metadata rather than media, and that the clip is "verified" — implying a lookup that can fail for unknown IDs — but says nothing about error behavior or pagination/size of the response.

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?

A single front-loaded sentence with the resource and scope stated immediately; no filler or redundant restatement of the title.

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?

An output schema exists, so return-value documentation is not required, and the annotations cover the safety profile. However, for a lookup tool keyed on an opaque ID, the description omits how to source clip_id and what happens when the clip is unverified or missing, leaving a real gap for correct invocation.

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 says nothing about clip_id — no format hint (the regex ^clip-\d{6}$ lives only in the schema) and, more importantly, no indication of where to obtain a valid clip_id (e.g., from search_clips). With one required parameter and no compensating text, the description adds no semantic value beyond the schema.

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?

States a specific verb ("Return") and resource ("catalogue metadata for one verified clip"), which is enough to distinguish it from download_clip (fetches media) and search_clips (finds clips). It stops short of explicitly naming those siblings, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given. The description never says to use this after search_clips to fetch details for a known clip_id, nor that it should not be used to retrieve the media itself (that is download_clip).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.