Skip to main content
Glama

add_group_memberships

Idempotent

Bulk-add learners to a student group to grant course access through visibility overrides. Provide the group ID and learner IDs in a single batch operation.

Instructions

Add learners to a student group. This is a BATCH operation.

    `id` is the group. `student_ids` are obfuscated learner ids.

    IDEMPOTENT: adding someone who is already a member succeeds and reports them as
    added. There is no "already a member" outcome, so a success here does not tell
    you the group changed. Duplicates inside one batch are first-wins; the later
    copies fail as `duplicate_in_batch`.

    An unknown group is a not-found error regardless of what else is in the request,
    so a failure here does not distinguish a bad group id from bad learner ids.

    Adding a learner to a group can GRANT COURSE ACCESS, because visibility overrides
    are attached to groups.

    Requires the `student-groups:write` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
student_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
totalYes
failedYes
group_idYes
succeededYes
student_idsYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description richly explains behavior: duplicate members are reported as added, duplicates in one batch are first-wins, unknown groups produce a not-found error, and adding members can grant course access. It also discloses the required OAuth scope. This far exceeds the minimal annotation information.

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, front-loading the core action and batch nature before covering idempotency, error semantics, side effects, and auth. Every sentence adds meaningful information, and the length is proportionate to the tool's behavioral complexity.

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 the tool's complexity, the description is highly complete: it explains batch behavior, idempotency nuances, duplicate handling, error semantics, the access-granting side effect, and required scope. An output schema exists, so return-value details are not the description's burden. Nothing essential is missing for correct invocation.

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 description coverage is 0%, but the description compensates by explicitly defining both parameters: 'id is the group' and 'student_ids are obfuscated learner ids.' It also adds behavioral meaning to student_ids by explaining duplicate handling inside a batch. It could still go deeper on value formats or constraints, but the core semantics are covered.

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: 'Add learners to a student group,' and immediately clarifies it is a batch operation. It clearly distinguishes itself from sibling tools like remove_group_memberships by naming the opposite action and the target entity.

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?

The description gives clear operational context: it is a batch add, idempotent, requires the student-groups:write OAuth scope, and can grant course access. It does not explicitly name alternatives or state when not to use it, but the direct purpose and prerequisites make usage fairly unambiguous.

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

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/CloudSecurityAlliance/csa-skilljar'

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