Skip to main content
Glama

create_user_group

Create a new user group in LearnWorlds with a title and courses, plus optional tags, managers, and enrollment rules.

Instructions

🟡 WRITE · creates data · POST /v2/user_groups

Creates a new user group. The endpoint response is the created user group resource.

Behavior: creates a record or triggers an action in the live school. Not idempotent: a repeated call can duplicate the effect. Auth (admin API token + Lw-Client id) is injected server-side, never by the model; calls are throttled to stay under LearnWorlds' 30-per-10s cap and retried on 429/5xx. Parameters: the whole JSON payload goes in the single body argument, forwarded verbatim (the spec leaves body optional, but this endpoint expects one). Returns: HTTP <status> followed by the LearnWorlds JSON response body. A non-2xx reply surfaces as a tool error with that status and the API error payload — 401 bad/expired token, 403 not permitted, 404 no such record, 422 rejected input. Use when: only when the user asked to create this. Check with a 🟢 read tool that the target exists and the record is not already there. Related User groups tools: add_user_user_group, deletes_user_group, get_user_group, get_user_groups, get_users_user_group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body (application/json).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the call is not idempotent and can duplicate effects, that auth is injected server-side, that calls are throttled and retried on 429/5xx, and that it operates on the live school. This is rich behavioral context consistent with annotations, with no contradiction.

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 well-structured with labeled sections: Behavior, Parameters, Returns, and Use when. Every sentence earns its place, and important operational facts are front-loaded without unnecessary repetition.

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?

Given there is no output schema, the description compensates by explaining the return format, error semantics and status codes, auth handling, rate-limit behavior, and pre-call checks. This is complete enough for an agent to invoke the tool correctly.

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 individual field semantics are already documented. The description adds key operational meaning: the entire payload goes in a single `body` argument, is forwarded verbatim, and although the spec marks `body` optional, this endpoint expects one. That warning goes 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?

The description uses a specific verb and resource: 'Creates a new user group' plus the endpoint 'POST /v2/user_groups'. It clearly identifies this as a create operation, and the related User groups tools list helps distinguish it from sibling read/update/delete operations.

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

Usage Guidelines5/5

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

The description states 'Use when: only when the user asked to create this' and instructs the agent to check with a read tool that the target exists and is not already there. It also lists the related sibling tools, giving clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ohneben/Learnworlds-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server