LearnUpon MCP Server and API by Cotlet

List enrollments in LearnUpon

learnupon_list_enrollments

Read-onlyIdempotent

List enrollments in the user's own LearnUpon account from ChatGPT, Claude or any AI agent. Returns how to do it in LearnUpon step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's LearnUpon Cloud Browser. LearnUpon's official API: LearnUpon has a REST API and a reporting MCP server, but neither covers day-to-day admin work from an AI agent (checked 20 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": "learnupon_list_enrollments"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds a non-obvious behavioral fact: 'opens nothing by itself' and returns screens, buttons, and fields instead of performing the action. The note that the vendor API was checked and does not cover this workflow also adds real context.

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 key correction ('opens nothing by itself') is front-loaded in the first sentence, and the sequencing guidance follows immediately. The third sentence about LearnUpon's API is a useful justification but is longer than necessary, and the 'from ChatGPT, Claude or any AI agent' phrasing is filler.

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, read-only guide tool with no output schema, the description supplies what matters: what comes back (screens, buttons, fields) and what to do next. Minor gaps remain around prerequisites such as an existing Cloud Browser session or configured LearnUpon account.

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 the baseline is 4 and no parameter explanation is required. The description correctly implies there are no inputs by framing the call as a guidance lookup.

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?

Names a specific verb and resource (list enrollments in the user's LearnUpon account) and immediately clarifies the actual output is a step-by-step how-to rather than the enrollment data itself. That correction is essential because the name otherwise implies a data query; the description prevents mis-selection but leaves a slight name/behavior mismatch an agent must reconcile.

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?

States the workflow explicitly: call this first to get instructions, then execute with cotlet_browser_* tools in the LearnUpon Cloud Browser, and explains why the official REST/reporting API is not an alternative. It does not say how this differs from cotlet_app_guide or whether a browser session must already exist.

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

All LearnUpon MCP Server and API by Cotlet tools Inspect

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

Need Help?