Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update post

update_post
Destructive

Change the title, text or category of a post you wrote, or any post as an admin. Edits a post in place, as Skool's Edit post does: fields you leave out stay as they are, and body replaces the whole text. Skool marks the post as edited. Your own posts, or any post when you are a group admin. By default you confirm each edit; 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>",
      "post_id": "<post_id>"
    },
    "name": "update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew text, replacing the old. Left out: unchanged.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
titleNoNew title. Left out: unchanged.
post_idYespost_id from list_posts (not the slug).
categoryNoMove the post to this category, by name.

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?

Adds substantial behavior beyond the annotations: omitted fields stay unchanged, body replaces the entire text, Skool stamps the post as edited, a confirmation prompt is on by default and can be switched off, and the call waits for the owner's approval. These are exactly the consequences an agent needs before invoking a destructiveHint=true mutation.

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 purpose is front-loaded, but the permission scope is stated twice ('a post you wrote, or any post as an admin' then 'Your own posts, or any post when you are a group admin'), and the clause 'as Skool's Edit post does' is filler that costs a sentence without informing the agent.

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 destructive, non-idempotent mutation with no output schema, the description covers permissions, partial-update semantics, confirmation behavior and the approval wait. The main omission is what the tool returns after a successful edit or what happens on rejection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the partial-update contract (left-out fields unchanged) and that body is a full replacement rather than an append, which the per-parameter descriptions only state tersely.

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?

States a specific verb (change) and the exact editable fields (title, text, category) of a specific resource (a post), plus a permission scope. It is clearly distinguishable from create_post and delete_post by the operation described, though no sibling is named explicitly.

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 the eligibility rule plainly: your own posts, or any post if you are a group admin. It also clarifies in-place editing semantics, but it never contrasts itself with adjacent tools such as create_post or delete_post or says when an edit is the wrong choice.

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