Skip to main content
Glama

TT Uni Course Media

tt_uni_course_media

Give a course its cover image or promo video from a FILE (for a file already online, use tt_uni_update_course cover_url / cover_video_url). WRITES: start reserves an upload link and changes nothing on the course yet; complete attaches the file, replacing the current cover or promo video. Two steps: - action=start: course_id, kind = cover (JPG/PNG/WebP up to 5 MB, at least 640 x 360, cropped to 16:9 at 1280 x 720) or cover_video (MP4/WebM up to 50 MB, plays at the top of the course page), filename, size_bytes, rights_confirmed=true (the teacher owns or may use the file). Returns upload_url, headers and upload_token. PUT the file to upload_url with exactly those headers (one request; the link lasts 30 minutes). - action=complete: course_id + upload_token. Tradetron checks the file as a Studio upload is checked and attaches it. On a teacher's approved course it waits for Tradetron's approval (pending_review). Needs a sandbox that can make HTTP requests; otherwise the teacher uploads it in Studio.

TT Uni is Tradetron's course marketplace (tradetron.tech/learn). These tools act as the signed-in user and work only for approved TT Uni teachers; anyone else is pointed to https://tradetron.tech/learn/teach. DRAFTS ONLY: nothing is published until the TT Uni review team approves the course. TT Uni teaching rules: no tips or buy/sell calls; no promised returns and no P&L screenshots as proof; any market data shown must be at least 30 days old; disclose any paid strategy of your own that the course mentions. Prices are in INR and exclude GST (18% is added at checkout); the teacher earns 50% of the price. AUTH-REQUIRED.

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": {
      "action": "<action>",
      "course_id": "<course_id>"
    },
    "name": "tt_uni_course_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNostart: cover | cover_video
actionYesstart | complete
filenameNostart: the file's name, with its extension
course_idYes
size_bytesNostart: the file's exact size in bytes
upload_tokenNocomplete: from start
rights_confirmedNostart: true once the teacher confirms they may use the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: start changes nothing on the course yet, complete replaces the current cover or promo video, the upload link lasts 30 minutes and must be used with exactly the returned headers in one request, and approved courses go to pending_review. It also discloses the auth constraint (approved TT Uni teachers only) and hard file limits (5 MB / 640x360 cropped to 16:9; 50 MB MP4/WebM). Note that 'complete replaces the current cover' is a mutation nuance not conveyed by destructiveHint=false, but it is disclosed rather than contradicted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action, the sibling disambiguation and the two-step mechanics are front-loaded and tightly structured with bullets. Deductions for the trailing block on INR pricing, GST and the 50% revenue split, which is boilerplate policy that does not help an agent select or invoke this media tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, two-phase tool with no output schema, the description supplies everything needed: required inputs per phase, the exact HTTP follow-up, the return shape (upload_url, headers, upload_token), and the post-complete review state. Nothing an agent must know to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 86% schema coverage, the description adds substantial meaning: kind is bounded to cover | cover_video with per-kind formats and size/resolution rules, rights_confirmed is explained as the teacher's ownership confirmation, and upload_token is described as flowing from start into complete.

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?

Opens with a specific verb and resource: give a course its cover image or promo video from a FILE. It immediately distinguishes itself from tt_uni_update_course, which handles files already online via cover_url / cover_video_url.

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?

Explicitly names the alternative (tt_uni_update_course with cover_url / cover_video_url) for an already-hosted file, spells out the two-step start/complete sequence, and adds the fallback condition: a sandbox that can make HTTP requests is required, otherwise the teacher uploads in Studio.

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