Skip to main content
Glama

list_groups

Read-onlyIdempotent

List student groups to identify which learners can access published courses. Filter by group name or category, and page through results when more than one page exists.

Instructions

List student groups, one page at a time.

    Group membership drives which published courses a learner can see, so this is
    the starting point for any "who can access what" question. Results are one page:
    when has_more is true, call again with next_cursor.

    `filter_name` is a case-INSENSITIVE substring match. Note that group names
    themselves are case-SENSITIVE and unique, so "Staff" and "staff" can both exist
    and this filter will return both.

    `filter_category_id` takes an obfuscated StudentGroupCategory id. An unknown or
    cross-organization id returns zero results rather than an error, so an empty
    list here does not prove the category does not exist.

    Each group carries `updated_at` - most other Skilljar objects call this field
    `modified_at`.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNo
filter_nameNo
page_cursorNo
filter_category_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
groupsYes
has_moreYes
next_cursorNo
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds substantial behavioral detail: the has_more/next_cursor pagination contract, case-insensitive filtering against case-sensitive unique group names, the zero-results-not-error behavior for unknown or cross-organization category ids, and the updated_at vs modified_at naming quirk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and each subsequent paragraph delivers one distinct actionable fact (pagination, filter semantics, category-id behavior, field-name quirk, auth scope) with no filler. The prose is slightly expansive in places, but every sentence earns its place.

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?

With the output schema present and annotation-covered safety, the description supplies all remaining operational knowledge: how to paginate, how each filter behaves at the edges, the required OAuth scope, and a schema naming deviation. An agent has everything needed to call this tool correctly.

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?

Schema description coverage is 0%, so the description carries the full burden for parameter meaning — and it delivers. It explains filter_name's case-insensitive substring matching, filter_category_id's obfuscated-id and zero-result semantics, and the pagination relationship between page_size, page_cursor, has_more, and next_cursor.

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?

Opens with a specific verb and resource — 'List student groups, one page at a time' — which clearly states both scope and pagination behavior. It is immediately distinguishable from sibling group tools such as get_group, create_groups, update_groups, delete_groups, and list_group_categories.

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 frames the tool's role with domain context: group membership drives published-course visibility, making this 'the starting point for any "who can access what" question.' It does not, however, name exclusions or route the agent to a sibling like get_group when a single group is needed.

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