Skip to main content
Glama

Upload lesson files

create_lesson_upload_session
Idempotent

Creates an MP4/PDF upload session for specified lessons in a course draft. Requires course and lesson IDs, but no file data; file selection happens afterward in the Trainn uploader. Chat attachments are not accessible to this tool and cannot be transferred into Trainn. Supported hosts display an in-chat uploader; other hosts receive a standalone upload link. get_course_build_status or get_lesson_upload_status reports progress after file submission. General Library uploads without a lesson destination 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>",
      "lesson_ids": "<lesson_ids>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_lesson_upload_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
lesson_idsYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the write/idempotent/openWorld profile, while the description supplies the behavior that actually matters: no file bytes are accepted here, selection happens out-of-band in the Trainn uploader, and the response differs by host (in-chat uploader versus standalone link). It also discloses a hard limitation on chat attachments.

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?

Front-loaded with the core action, then constraints, then next steps, then the sibling alternative. Five tight sentences with no redundant restatement of the title or schema.

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?

Covers preconditions, follow-up tools, host-dependent behavior, and exclusions for a three-parameter creation tool with no output schema. The one gap is what the call actually returns (session identifier or upload URL), which the agent must infer since no output schema exists.

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?

With 0% schema description coverage the description must carry the load; it explains that course_id and lesson_ids identify the destination and that no file data belongs here. The third parameter, idempotency_key, is never mentioned, and nothing is said about the multi-lesson (up to 20) nature of lesson_ids beyond 'specified lessons'.

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: creates an MP4/PDF upload session scoped to lessons in a course draft. It explicitly separates itself from the near-identical create_library_upload_session by naming that sibling for lesson-less uploads.

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

Usage Guidelines5/5

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

Gives the selection condition directly: use this tool when there is a lesson destination, use create_library_upload_session for general Library uploads. It also rules out a tempting misuse (chat attachments cannot be transferred) and routes progress checks to get_lesson_upload_status or get_course_build_status.

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