Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Follow post

follow_post
Destructive

Get notified of new comments on a post, or stop. Follows a post so new comments land in your Skool notifications, as the post menu's Follow does; following false unfollows. You follow your own posts from the start. Changes only your own notifications, so it runs without asking first.

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

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
post_idYespost_id from list_posts (not the slug).
followingNofalse stops the notifications. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations flag destructiveHint=true, but the description usefully narrows that: the effect is confined to your own notification subscription and is safe to run without confirmation. That is real context beyond the structured hints. It doesn't describe the response or whether re-following an already-followed post is a no-op, which is the remaining gap given 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.

Conciseness5/5

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

Three short clauses, front-loaded with the core action and behavior, with no filler. Every sentence carries information an agent needs.

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 toggle with no output schema and full schema coverage, the description supplies the states, the default, and the permission posture — enough to invoke correctly. A note on what a successful call returns or whether follow is a no-op when already following would close the last gap.

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%, so `group`, `post_id`, and `following` are already documented. The description's "following false unfollows" largely restates the schema's "false stops the notifications" and adds no new syntax or edge-case detail, 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?

The description opens with a concrete verb and resource ("Get notified of new comments on a post, or stop") and immediately grounds it in a known UI behavior ("as the post menu's Follow does"). This clearly distinguishes it from sibling interactions like comment_on_post or like_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?

It states the toggle semantics ("following false unfollows") and a useful precondition ("You follow your own posts from the start"), plus consent guidance ("changes only your own notifications, so it runs without asking first"). It stops short of naming any alternative tool, though no real sibling alternative exists for this action.

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