Skip to main content
Glama

Upload course cover

create_course_cover_upload_session
DestructiveIdempotent

Creates a JPEG/PNG upload session for the cover of a specified course draft. Requires a course ID and revision, but no file data; file selection happens afterward in the Trainn uploader. Chat attachments and base64 image data are not supported inputs. The image must be at least 1440×780 pixels. Supported hosts display an in-chat uploader; other hosts receive a standalone upload link. A successful upload applies the cover to the draft. General Library MP4/PDF uploads use create_library_upload_session.

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>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_course_cover_upload_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare mutation, destructiveness, idempotency and open-world behavior, yet the description still adds real context beyond them: the two-step nature of the operation, the host-dependent delivery (in-chat uploader vs standalone link), the minimum image dimensions, and the fact that a successful upload applies the cover to the draft. It stops short of saying whether an existing cover is replaced or how the session is finalized.

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?

Six short sentences, front-loaded with what the tool creates and what it needs, then constraints, then host behavior, then the sibling pointer. Every sentence conveys a distinct operational fact with no restatement of the tool name or 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 covers the important workflow facts (no file payload, uploader vs link, image size minimum, cover applied on success), which is close to sufficient for a session-creation tool. The main residual gap is the shape of the returned session (identifier or URL lifetime) and the meaning of the revision and idempotency parameters.

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%, so the description must carry the parameter meaning, and it only partly does. It names course_id and expected_revision but never explains what a revision is, where to obtain it, or what happens on a stale value (optimistic concurrency), and idempotency_key is never mentioned at all.

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?

The description opens with a specific verb and resource: 'Creates a JPEG/PNG upload session for the cover of a specified course draft.' It explicitly distinguishes itself from the sibling that handles the similar-but-different case ('General Library MP4/PDF uploads use create_library_upload_session'), so an agent can route correctly without inspecting schemas.

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?

It states the key precondition of the flow ('Requires a course ID and revision, but no file data; file selection happens afterward') and gives explicit exclusions ('Chat attachments and base64 image data are not supported inputs'). It names one alternative for library uploads but does not address the nearest siblings such as create_lesson_upload_session or set_course_cover_video, so guidance is clear but not exhaustive.

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