Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Pin post

pin_post
Idempotent

Pin a post to the top of a Skool feed or Classroom page, or unpin it to control visibility. Admins only.

Instructions

Pin a post to the top of the feed (up to 3) or to a Classroom page (up to 12). Admins only.

Pins a post to the top of the feed, where Skool allows up to 3 pinned posts, or to a Classroom page, which allows up to 12. Set pinned to false to unpin. Admins only. pin_post runs without asking first: pinning sends nothing to anyone and is undone with one call.

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": "pin_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
pinnedNofalse unpins. Default: true.
post_idYespost_id from list_posts (not the slug).
course_page_idNoPin to this Classroom page instead of the feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the bar is lower, yet the description adds real context: admin-only authorization, the 3/12 capacity ceilings, and the one-call undo path. The 'sends nothing to anyone' and no-confirmation note is useful beyond what the annotations convey, though capacity-exceeded behavior is still unstated.

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 second paragraph is largely a restatement of the first sentence, repeating the 3/12 limits and 'Admins only' verbatim. The key facts are front-loaded, but redundancy costs it points.

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 mutation tool with a full schema and annotations but no output schema, the description covers authorization, capacity, undo, and unpin semantics. Only failure behavior at the pin cap is missing, which is a minor 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 all four parameters are already documented in structured fields including pinned=false and course_page_id. The description reinforces the unpin flag and the feed-vs-classroom-page choice but adds no syntax or edge-case detail beyond the schema, so 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?

Names a specific verb and resource and adds scope: pinning to the feed (max 3) versus a Classroom page (max 12). The agent can distinguish this from pin_comment and update_post 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?

Explicitly states the two destinations, that pinned=false unpins, and that admins only may call it, which is clear usage context. It stops short of naming sibling alternatives (e.g. pin_comment for comments, update_post for edits), leaving that routing to inference.

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