Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List membership requests

list_membership_requests
Read-onlyIdempotent

Pending requests to join, with each applicant's Membership Questions answers. Admins and moderators only. Lists requests to join a private group, 30 to a page, oldest first within the page, with the answers each applicant gave to your Membership Questions. Only admins and moderators see requests; other accounts get APP_PERMISSION_DENIED. Pass request_id to approve_membership_request or decline_membership_request.

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_membership_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
limitNo1 to 30. Default: 30.
cursorNoNext page cursor from the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real context beyond that: pagination shape (30 per page, oldest first), the permission failure code, and the fact that each entry carries applicant answers plus a request_id. It stops short of describing the response envelope or whether a missing cursor means no more pages.

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?

The opening sentence and the second sentence say substantially the same thing ('pending requests to join, with each applicant's Membership Questions answers' vs. 'lists requests to join a private group... with the answers each applicant gave'), which is wasted space. The valuable parts (permissions, denial code, pagination, downstream tools) are appended rather than front-loaded.

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?

With no output schema, the description does carry return-value information: applicants' answers, request_id for downstream approve/decline calls, and page size/ordering. Enough for an agent to call and chain it correctly, though the response structure and end-of-pagination behavior remain implicit.

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

Parameters3/5

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

Schema coverage is 100%, so group, limit and cursor are already documented, and the description mostly paraphrases them ('30 to a page' restates the default limit). The mention of request_id is useful but refers to a returned field, not an input, which slightly muddies rather than clarifies the inputs. Baseline 3 applies.

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 (list pending requests to join a private group) and its scope (30 per page, oldest first within page, includes Membership Question answers). It is clearly distinct from siblings approve_membership_request and decline_membership_request, and from list_members.

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 the audience restriction (admins and moderators only) and the exact failure mode for others (APP_PERMISSION_DENIED), and routes the agent forward by naming the two sibling tools that consume the returned request_id.

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