Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete group link

delete_group_link
Destructive

Deletes a specific sidebar link from a Skool group by number and returns the updated link list. Use it to manage group navigation; admin access required.

Instructions

Remove a link from the group's sidebar. Admins only.

Removes one sidebar link, as Settings, Links, Delete does; the links after it move up a number. Returns the whole new list. Admins only.

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>",
      "number": "<number>"
    },
    "name": "delete_group_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
numberYesLink number from list_group_links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description explains two important behaviors: subsequent links move up a number, and the operation returns the whole new list. It does not discuss failure modes or whether removal can be undone, but it meaningfully supplements the annotations.

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 description is short and front-loads the core action, but 'Admins only' is repeated in both sentences without adding new information. The second sentence is otherwise efficient and informative.

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 mutation with no output schema, the description covers the action, admin restriction, numbering side effect, and return value. Remaining gaps around error handling or reversibility are minor given the annotations and fully documented parameters.

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 parameter descriptions already carry most meaning. The description still adds useful context by explaining that deleting one link shifts the numbering of links after it, which clarifies the significance of the 'number' parameter.

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?

The description states a specific verb and resource: 'Remove a link from the group's sidebar.' It is immediately distinguishable from sibling tools like add_group_link, update_group_link, and list_group_links, and it clarifies that exactly one sidebar link is removed.

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?

It gives the key prerequisite, 'Admins only,' and grounds the action in the familiar UI path 'Settings, Links, Delete.' It does not explicitly name alternatives such as update_group_link or list_group_links, but the intended use is clear.

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