Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Rename level

rename_level

Set a custom title for any of a group’s nine levels so members see a clearer rank name; submit an empty title to restore Skool’s default.

Instructions

Give one of the group's 9 levels its own title. Admins only.

Sets the title members see next to a level, as Settings, Gamification does; an empty title goes back to Skool's plain name. The points needed per level are Skool's and do not change. Admins only. Runs without asking first: undone with one call.

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>",
      "level": "<level>",
      "title": "<title>"
    },
    "name": "rename_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
levelYesLevel number, 1 to 9.
titleYesThe title members see at that level. Empty string: back to the plain name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: the change is applied without a confirmation prompt ('Runs without asking first') and is reversible in one call, and the per-level point thresholds are explicitly unaffected. That said, it never mentions rate limits or side effects such as member notifications, and the claim of one-call reversibility sits slightly awkwardly against idempotentHint=false.

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?

Front-loaded with the action and the auth constraint, and the 'what changes / what does not change' split is useful. Minor waste: 'Admins only' appears twice, and the 'as Settings, Gamification does' clause is confusing rather than clarifying.

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 who may call it, what is modified, what is preserved, and how to undo it. Only the return value and any downstream effects on members are unstated, which are minor omissions here.

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 description coverage is 100%, so group, level and title are already fully documented, including the empty-string reset behavior. The description restates the level range and empty-title semantics rather than adding new syntax or format guidance, so the baseline of 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 with scope: 'Give one of the group's 9 levels its own title.' An agent can immediately tell this apart from the read-only siblings list_levels and get_leaderboard, and knows the target object is a level title, not a level threshold.

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?

Clear operating context: admin-only, it modifies what members see next to a level, and an empty title reverts to the plain name. It never names an alternative call or states an exclusion, but for a single-purpose setter the applicability conditions are effectively covered.

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

Deploy Server

Other Tools