Skip to main content
Glama

TT Uni Update Course

tt_uni_update_course
DestructiveIdempotent

Update one of the teacher's courses. Pass EXACTLY ONE of: - markdown: the whole course (start from tt_uni_get_course's markdown, keep the id: lines). Fields are replaced; chapters and lessons are matched by id line (else position); new ones are added; ones you left out are NOT deleted — they come back in warnings. - fields: only course-level fields to change, any of title, summary, description, price_inr, level, topics[], outcomes[], prerequisites (free text shown on the page), kind (draft only), cover_url, cover_video_url = https link to an .mp4/.webm promo video played at the top of the course page with the cover as its poster (null removes it; a YouTube/Drive/Dropbox PAGE does not play; a file on the teacher's computer is uploaded in Studio > course > Promo video). TT Uni admins only: prerequisite_course_id = the id of the course a learner must FINISH (80% watched + required tests passed) before a free or plan course opens; 0 removes it. A priced course only shows "Recommended: finish it first"; learners already enrolled keep it. Limits: title 160, summary 255, prerequisites 255, each outcome 200 characters (a dash or apostrophe counts once); over a limit is refused with the limit, never cut. Replies with a compact summary (ids, titles, status, changed = the fields you sent as now stored, warnings); response="full" returns the whole course. If it answers TTUNI_WRITE_UNCONFIRMED, read the course back before trying again. Overwrites what it touches; confirm changes with the teacher first.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
markdownNo
responseNosummary (default) | fullsummary
course_idYes

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?

Annotations already declare destructive=true and idempotent=true, and the description reinforces this with concrete mechanics: fields are replaced, omitted chapters/lessons are NOT deleted but echoed in warnings, and over-limit values are refused rather than truncated. It goes further with auth scoping (approved teachers only), the drafts-only publication model, and the read-back-before-retry protocol.

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?

Front-loaded with the mode-selection rule and organized as scannable bullets, so the length is largely earned. A few passages, such as the GST/revenue-share and Studio promo-video upload instructions, sit at the edge of relevance to an update call.

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?

Covers everything needed for a 4-parameter destructive mutation with no output schema: return shape (compact summary plus `changed`, or full course via response="full"), overwrite behavior, character limits, write-confirmation failure handling, and authorization requirements.

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?

Schema coverage is only 25% (just `response`), and the description fully compensates: it defines the two exclusive modes, enumerates every accepted `fields` key, and specifies behavior for the subtle ones (cover_video_url must be a direct .mp4/.webm link, null removes it, prerequisite_course_id requires 80% watched, 0 removes it) plus exact character limits per field.

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 ("Update one of the teacher's courses") and immediately enumerates the two mutually exclusive edit modes. It also distinguishes itself from sibling chapter/lesson editors by explaining that markdown mode matches chapters and lessons by id line, so an agent can tell when whole-course update is the right call.

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 constrains invocation with "Pass EXACTLY ONE of" and then defines when to use each mode. It names tt_uni_get_course as the required source for markdown, tells the agent to confirm changes with the teacher first, and flags the TTUNI_WRITE_UNCONFIRMED retry path.

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