Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Ban member

ban_member
Destructive

Ban a member from the group, optionally deleting their recent posts. Admins only. Bans one member, as Membership settings, Ban does: they lose access and cannot ask to join again. delete_recent_posts also removes their recent posts and comments, which cannot be undone. A paid member's subscription is not cancelled by this. remove_member lifts a ban. Admins and moderators. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
member_idNomember_id from list_members; needed with delete_recent_posts.
membership_idYesmembership_id from list_members.
delete_recent_postsNoAlso delete their recent posts and comments, as Skool offers. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint, openWorldHint, idempotentHint=false) by disclosing that delete_recent_posts is irreversible, that a paid subscription is not cancelled, that each call is confirmed by default with an opt-out, and that the call waits for owner approval. These are exactly the operational traits an agent needs before invoking a destructive tool.

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?

Destructive scope and admin restriction are front-loaded, which is right, but the middle section is choppy and repetitive ('as Membership settings, Ban does') and the standalone fragment 'Admins and moderators.' reads as contradictory leftovers. Every sentence is informative, but the phrasing costs clarity.

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 destructive, approval-gated mutation with no output schema, the description covers irreversibility, side effects (subscription untouched), confirmation behavior, and approval latency. The only real gap is the unresolved whether-moderators-can-ban ambiguity and the member_id/membership_id relationship.

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, but the description adds real semantic weight beyond the schema: delete_recent_posts is irreversible and also removes comments, and the tool acts on a single member. It does not explain the member_id vs membership_id distinction, which remains a schema-only detail.

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 ('Ban a member from the group') plus the optional scope ('optionally deleting their recent posts'). It explicitly distinguishes itself from the sibling remove_member ('remove_member lifts a ban') and clarifies batch scope with 'Bans one member', so an agent can pick it without opening the 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?

Gives a clear precondition ('Admins only') and names the contrasting alternative ('remove_member lifts a ban'), which is the key routing decision. It stops short of a full when-not-to-use rule and the later fragment 'Admins and moderators' muddies the permission condition it just set.

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