Skip to main content
Glama

update_groups

Batch update student group fields by ID. Send full email-domain lists because values replace arrays, and use null to clear category.

Instructions

Change student groups. This is a BATCH operation.

    Every item needs an `id`. Groups have no stable natural key - names are
    renameable, so a name is not durable enough to identify one across calls.

    TWO BEHAVIOURS THAT LOSE DATA IF YOU ASSUME THE OPPOSITE:

    `rule_email_domains` REPLACES the whole stored array. It does not merge. To add
    one domain, send every existing domain plus the new one; sending only the new one
    deletes the rest.

    `category_id: null` CLEARS the category. Omitting the key leaves it unchanged.
    These are different requests, so do not send an explicit null unless you mean
    "remove this group from its category".

    At least one changeable field per item is required.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
noteYes
totalYes
failedYes
succeededYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

Reveals non-obvious, potentially destructive behaviors: rule_email_domains replaces rather than merges, category_id: null clears while omission leaves unchanged, and at least one changeable field is required. This goes well beyond the minimal annotations and also covers required OAuth scope.

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?

Every sentence in the description adds a necessary constraint or warning. The structure front-loads the batch nature and then organizes the dangerous edge cases under a clear warning heading.

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?

For an opaque-schema batch mutation, the description is complete: identity requirement, partial-update minimum, replace/merge hazard, null-clear semantics, and required OAuth scope. The existing output schema removes the need to document return values.

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

Parameters5/5

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

The input schema is opaque (groups array with additionalProperties: true, 0% coverage), so the description carries the full burden. It explains the item id requirement, replace semantics for rule_email_domains, null-vs-omitted behavior for category_id, and the minimum changeable-field requirement.

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?

States 'Change student groups' and immediately defines scope as a batch operation that mutates existing groups via IDs. This distinguishes it from create_groups, delete_groups, and membership tools even without naming them.

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?

Provides clear operational context: batch update, every item needs an id, name cannot be used as durable key, and requires student-groups:write scope. It does not explicitly name alternatives or state when not to use this tool, so it stops at clear context without exclusions.

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