Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Set member role

set_member_role
Destructive

Make a member an admin or moderator, or back to a member. Admins only. Changes one member's role, as the member's Membership settings do: admin (full control), moderator (can remove posts and members) or member. Skool allows moderators only on the Pro plan. The group owner keeps their role. 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>",
      "role": "<role>"
    },
    "name": "set_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesadmin, moderator or member.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
membership_idYesmembership_id from list_members.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say it is a destructive, non-read-only mutation; the description adds authorization requirements (admins only), a plan-level constraint (Pro for moderators), an invariant (owner keeps their role), and an approval/confirmation flow ('waits for the owner's approval', confirm-by-default with an opt-out). That is substantial disclosure beyond the structured hints.

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 action and scope are front-loaded and sentences are short. The confirmation sentences at the end partially repeat each other ('you confirm each call' vs 'waits for the owner's approval'), costing a little tightness.

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 3-parameter mutation with no output schema, the description covers permissions, plan limits, side effects, and the approval gate. It omits what the call returns or how to detect a no-op role assignment, a minor remaining gap.

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 meaning: it explains what each enum value grants (admin = full control, moderator = can remove posts and members, member = default). It doesn't further explain group/membership_id, which the schema already covers.

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 ('Make a member an admin or moderator, or back to a member') and scopes it to exactly one member, which cleanly separates it from siblings like ban_member or remove_member. The role vocabulary is named up front.

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 clear preconditions: admins only, moderators require the Pro plan, and the group owner is unaffected. It does not explicitly route to alternatives (e.g., use ban_member/remove_member for removal), but the positive usage context is unambiguous.

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