Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List videos

list_videos
Read-onlyIdempotent

Videos in the group's Classroom lessons and feed posts, uploaded or linked. Lists the videos this account can watch: one per Classroom lesson with a video, in course order, and the videos in the newest feed posts (post_pages pages of 30). An uploaded video has a video_id and transcript true: pass it with its course_id and lesson_id, or post_id, to get_video_transcript. A linked one (YouTube, Vimeo, Loom, Wistia) has only video_url. Locked courses are named in locked_courses, without their videos.

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>"
    },
    "name": "list_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
whereNoClassroom lessons, feed posts, or both (default).
post_pagesNoFeed pages to scan for post videos, newest first, 30 posts each. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent profile; the description adds real behavioral detail beyond them — feed scanning is bounded to (post_pages × 30) newest posts, Classroom results come one per lesson in course order, and locked courses are reported in locked_courses without their videos. Those are exactly the 'what you get and what you don't' facts an agent needs.

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 resource and its scope, then the per-source behavior, then the handoff to get_video_transcript. It is a single dense paragraph that runs slightly long, but essentially every clause carries information the agent would otherwise have to guess.

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?

There is no output schema, yet the description covers the return shape well — video_id + transcript for uploads, video_url for links, ordering for lessons, and the locked_courses side channel. For a 3-parameter read tool, nothing material is missing.

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 the baseline is 3, and the description still adds meaning: post_pages is characterized as pages of 30 newest-first posts, and the course_id/lesson_id vs post_id pairing needed downstream is spelled out. The 'where' enum values are only implied in prose rather than mapped one-to-one.

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?

The description names a specific verb and resource ('Lists the videos this account can watch') and immediately scopes it to two sources: Classroom lessons and feed posts. It distinguishes uploaded vs linked videos and explicitly routes to the sibling tool get_video_transcript, so an agent can tell it apart from list_posts/get_lesson without opening a schema.

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?

It gives clear context for use: videos available to this account, split by Classroom and feed, and tells the agent to pass video_id with course_id/lesson_id or post_id to get_video_transcript. It does not state exclusions, e.g. that list_posts should be preferred when the goal is post content rather than videos.

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