Skip to main content
Glama

Set cover video

set_course_cover_video
DestructiveIdempotent

Sets an existing visible, published Trainn video as the course cover. Search Library content first and let the user choose the video. This replaces the current cover image.

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": {
      "course_id": "<course_id>",
      "video_id": "<video_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "set_course_cover_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYes
course_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds the crucial consequence the annotations cannot express: 'This replaces the current cover image.' It also adds an eligibility precondition (video must be visible and published). It says nothing about what happens when expected_revision is stale, which is a meaningful omission for a destructive mutation.

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?

Three short sentences, front-loaded with the effect and destruction warning, then the required workflow, then the consequence. Zero filler.

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?

For a destructive mutation with no output schema and four required parameters at 0% schema coverage, the description covers the effect and the source-eligibility rule but leaves two non-obvious required parameters undefined and does not describe the failure mode on revision mismatch. Adequate but with clear gaps.

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 coverage is 0%, so the description must carry all four parameters. It does supply real meaning for video_id (must be an existing visible, published video) and implies course_id, but expected_revision and idempotency_key — the concurrency and retry-safety controls — are never explained, leaving the agent to guess their purpose and failure semantics.

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 ('Sets ... video as the course cover') and constrains the source to an 'existing visible, published Trainn video', which cleanly separates it from the upload-session sibling that creates a new cover asset.

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?

Gives an explicit workflow precondition ('Search Library content first and let the user choose the video'), which tells the agent it must not invent a video_id. It does not name a specific alternative tool for the upload path, so the routing guidance is not fully complete.

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