Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get members, churn and MRR in Skool

skool_get_members_churn_and_mrr
Read-onlyIdempotent

Get members, churn and MRR in the user's own Skool account from ChatGPT, Claude or any AI agent. Returns how to do it in Skool step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Skool Cloud Browser. Skool's official API: Skool has no public API and no developer docs (checked 10 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skool_get_members_churn_and_mrr"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotent and non-destructive, so safety is covered. The description adds real value beyond that by stating it 'opens nothing by itself' (no side effects whatsoever) and that Skool has no public API or developer docs, which explains the guide-based approach.

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

Conciseness3/5

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

Most sentences earn their place, particularly the no-public-API caveat. The middle sentence is a run-on that chains 'opens nothing by itself' into the browser-tool instruction, which slightly muddies where the tool's behavior ends and the follow-up workflow begins.

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

Completeness4/5

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

For a zero-parameter, no-output-schema tool, the description covers what it returns (instructions), what it does not do (open anything), and how to continue. It could be more specific about the shape of the returned guide, but nothing essential to invoking it 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?

The tool takes zero parameters, so there is nothing for the description to document. It correctly avoids inventing inputs and the empty schema matches the described behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear that this tool does not fetch data itself but returns a step-by-step walkthrough (screens, buttons, fields) for finding members, churn and MRR in Skool. This corrects the misleading name/title, which implies data retrieval. It stops short of 5 because an agent scanning only the name could still expect member data back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear workflow: call this first, then act with the cotlet_browser_* tools in the Skool Cloud Browser. It does not say when to prefer this over the many data-returning siblings such as list_members or skool_list_members, so routing between them is left implicit.

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