Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update membership question

update_membership_question
Destructive

Change a membership question. Admins only. Replaces one membership question with new text, type and answers. Requests already waiting keep the answers they gave. Returns all questions. Runs without asking first: nobody is notified.

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>",
      "question": "<question>"
    },
    "name": "update_membership_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotext (default), email or options (multiple choice, one answer).
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
numberYesQuestion number, from add_membership_question or get_group.
optionsNoUp to 4 answers when type is options.
questionYesThe question, up to 150 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it states that existing pending requests keep the answers they gave, that the tool returns all questions, that it runs without asking first, and that nobody is notified. These details are consistent with destructiveHint=true and materially help the agent understand the mutation's side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and constraint, then proceeds through replacement behavior, pending-request effects, return value, and confirmation behavior. Each short sentence adds useful information with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive admin mutation, the description covers the key context an agent needs: who can call it, that it replaces existing content, that pending answers are preserved, what it returns, and that it executes without confirmation. With a complete schema and helpful annotations, this is sufficiently complete.

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 the schema already defines group, number, question, type, and options. The description echoes 'new text, type and answers' but adds no parameter-level syntax or constraints beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Change a membership question.' It also clarifies the update semantics with 'Replaces one membership question with new text, type and answers,' which distinguishes it from add/delete siblings even without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Admins only' gives an important prerequisite, but the description does not explicitly say when to use this versus add_membership_question or delete_membership_question, nor when not to use it. Usage is therefore implied rather than fully guided.

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