Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Comment on post

comment_on_post
Destructive

Adds a comment to a Skool post or replies under an existing comment when parent_comment_id is set, appearing under your name.

Instructions

Comment on a post, or reply to a comment, as you.

Adds a comment to a post, or a reply under an existing comment when parent_comment_id is set. The comment appears under your name.

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>",
      "post_id": "<post_id>",
      "body": "<body>"
    },
    "name": "comment_on_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesComment text.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
post_idYespost_id from list_posts (not the slug).
parent_comment_idNocomment_id from get_post: reply under that comment instead of the post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare this as non-read-only, non-idempotent, open-world, and destructiveHint=true. The description adds useful identity context by saying the comment appears under your name, but it does not reconcile the destructiveHint=true annotation or explain visibility, moderation, or irreversibility.

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 definition is short and front-loaded. The second sentence somewhat repeats the first but earns its place by adding the parent_comment_id condition and the author-name detail.

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 simple four-parameter mutation with a fully described schema and safety annotations, the description gives enough context to invoke the tool correctly. It is weaker on side effects and does not explain the return value, though no output schema exists and this is not critical for invocation.

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 documents body, group, post_id, and parent_comment_id. The description only restates the parent_comment_id reply behavior without adding syntax, examples, or constraints beyond the schema.

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: commenting on a post or replying to a comment. It clearly separates the top-level comment case from the reply case, which is enough to distinguish it from siblings such as create_post, like_post, and follow_post.

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?

Explains that parent_comment_id makes the operation a reply under an existing comment rather than a top-level post comment. It does not name alternatives like create_post or set_post_comments, nor does it state exclusions, so it is clear but not fully routing-oriented.

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