Skip to main content
Glama

Import lesson link

import_lesson_content
Idempotent

Trainn downloads an MP4 or PDF from a publicly shared link and attaches it to an empty lesson, so no file has to travel through this conversation. The link must be readable by anyone who has it. Importing continues in the background: poll get_lesson_upload_status until it reports ready or failed.

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_id": "<lesson_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "source_url": "<source_url>"
    },
    "name": "import_lesson_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
course_idYes
lesson_idYes
source_urlYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, idempotent, non-destructive operation; the description adds genuinely new behavior, namely that the import is asynchronous with a terminal ready/failed state and must be polled. It does not explain what happens to title or existing lesson state, but the async model is the crucial disclosure and is present.

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 sentences, each earning its place: what it does, the precondition, and the async follow-up. The poll instruction is placed where the agent needs it, at the end of the call description.

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 an asynchronous mutation with no output schema, the description correctly covers the polling contract and the public-link prerequisite. However, it says nothing about the required concurrency and idempotency fields, which is a meaningful gap for a tool that creates state in an external system.

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% across six parameters, five of them required, so the description must compensate — and it largely does not. It never explains expected_revision (concurrency guard), idempotency_key (retry safety), or title, leaving the agent to guess at the most error-prone inputs; only source_url and lesson_id are indirectly implied.

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 mechanism: it downloads an MP4 or PDF from a publicly shared link and attaches it to an empty lesson. It also distinguishes itself from the direct-upload sibling path with the phrase "so no file has to travel through this conversation."

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 clear preconditions (publicly readable link, empty target lesson) and an explicit follow-up call to get_lesson_upload_status until ready or failed. It doesn't name when to prefer attach_lesson_content or import_library_content instead, so it falls short of full alternative routing.

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