Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get video transcript

get_video_transcript
Read-onlyIdempotent

The spoken text of a video uploaded to a lesson or post, from Skool's captions. Returns what is said in a video uploaded to Skool, as Skool's automatic captions, in 30-second segments with their start time. Give the video_id and where it is (course_id and lesson_id, or post_id), as list_videos returns them. One call reads about 20 minutes of video; when next_start_minute is not null, call again with it as start_minute for the rest (the first segment may repeat the last one). Linked YouTube, Vimeo, Loom or Wistia videos have no transcript here. Only videos this account can watch.

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": {
      "group": "<group>",
      "video_id": "<video_id>"
    },
    "name": "get_video_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
post_idNoFor a post video: post_id from list_videos.
languageNoCaption language code, e.g. 'en'. Default: the video's first caption track.
video_idYesvideo_id from list_videos (uploaded videos only).
course_idNoFor a lesson video: course_id from list_videos.
lesson_idNoFor a lesson video: lesson_id from list_videos.
start_minuteNoMinute to start from; pass next_start_minute of the previous answer to go on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description goes further by disclosing the ~20-minute-per-call read limit, the pagination contract via next_start_minute, and the caveat that the first segment may repeat. These are behavioral facts an agent cannot infer from structured fields.

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 what the tool returns, then input sourcing, then pagination, then exclusions. Dense without filler; every clause conveys operational information.

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?

No output schema exists, yet the description characterizes the return value (timestamped 30-second segments) and the continuation mechanism, covering the two things an agent must know to call and re-call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds real meaning on top by tying group/video_id/course_id/lesson_id/post_id to list_videos output and by explaining the start_minute ↔ next_start_minute pagination pairing. It stops short of detailing language track semantics, which the schema covers only minimally.

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 (get/returns) and resource (spoken text of a video) plus its source (Skool's automatic captions) and granularity (30-second segments with start time). Clearly distinguishable from list_videos, which it names as the ID source.

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 states what inputs to supply and where they come from (course_id/lesson_id or post_id, as list_videos returns them), and adds exclusions: linked YouTube/Vimeo/Loom/Wistia videos have no transcript here, and only videos this account can watch are accessible. That is genuine when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skool MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources