Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update group About text

update_group_about
Destructive

Replace the text on the group's About page. Admins only. Replaces the description on the group's About page, the one visitors read before they join, as editing it on the About page does. Images and videos on the page stay. Everyone who opens the page sees the change, so 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>",
      "about": "<about>"
    },
    "name": "update_group_about"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboutYesThe new About text, replacing the old. Plain text, line breaks kept.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds context annotations cannot express: images and videos on the page survive the replacement, the change is immediately visible to all visitors, a confirmation step is on by default, and the call waits for owner approval. That is unusually rich disclosure for a mutation 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?

The lead sentence is front-loaded and the side-effect facts earn their place, but the third sentence restates the first ('Replaces the description on the group's About page...') and the clause 'as editing it on the About page does' is circular filler. Trimming one sentence would improve it with no loss.

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 two-parameter mutation tool with no output schema, the description covers permissions, side effects, visibility, confirmation, and approval. The only soft spot is that 'waits for the owner's approval' leaves the return/blocking behavior ambiguous, which matters since there is no output schema to fall back on.

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% and both parameters are fully documented there ('about' as plain text with line breaks kept, 'group' as a URL name). The description adds no parameter-level detail beyond noting the About text replaces the old one, so the 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 ('Replace the text on the group's About page'), plus the permission boundary ('Admins only'). This is clearly distinguishable from siblings like update_group_link, update_group_rule, and update_membership_question without opening any 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 prerequisite (admins only) and invocation context (confirmation is on by default but can be switched off for this tool), which is exactly what an agent needs before calling. It stops short of naming alternatives or explicit when-not conditions, so it lands just below the top band.

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