Skip to main content
Glama

Put games in lists

set_activity_folders
DestructiveIdempotent

Put games into lists of the current user (the Lists of My games), take them out or move them from one list to another. With mode "add" the games go into the lists in "folders" and stay in the ones they were in; with "remove" they leave those lists; with "set", the default, each game ends up in exactly the lists in "folders", so "set" with an empty "folders" takes it out of all its lists. To move a game, send "set" with its new lists, or "remove" from one list and then "add" to the other. Taking a game out of a list never deletes it. Lists only show published games: with scope "all" only published games are taken, while games chosen by id go in whatever their state, and the unpublished ones do not show in the list. Ids of lists of other users are ignored. Choose the games by id, at most 50 per call, or with scope "all", every game that matches the filters ("folder", "type", "q2", "state") except those in "exclude": then each call handles one batch, and while "hasMore" is true you call again with "nextCursor" as "before". Same as POST users/{idUser}/activities/ with action=setFolders of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response". There "ok" lists the games changed and "failed" the ones that could not be, with the reason.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_activity_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
q2NoWith scope "all": only the games whose title, description or labels contain this text.
idsNoIds of the games, from list_my_activities or list_folder_activities. Not used with scope "all".
modeNoHow "folders" is applied: "set" (the default), "add" or "remove".
typeNoWith scope "all": only the games of this activity type.
scopeNo"all" to act on every game that matches the filters instead of on "ids".
stateNoWith scope "all": only the games in this state.
beforeNoWith scope "all": "nextCursor" of the previous batch. Omit it for the first batch.
folderNoWith scope "all": only the games of this list.
lengthNoWith scope "all": games per batch, at most 50, which is also the default.
excludeNoWith scope "all": ids of games to leave out.
foldersNoIds of the lists, from list_my_folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds non-obvious behavior they cannot express: removing a game from a list never deletes the game, lists only display published games, id-selected unpublished games are placed but remain invisible, other users' folder ids are silently ignored, and there is a hard cap of 50 games per call with cursor batching. It also discloses the response shape ("ok" and "failed" with reasons), which matters because no output schema exists.

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?

There is little filler and the purpose leads, but the content is delivered as one dense run-on paragraph that blends mode semantics, publication caveats, pagination, and API mapping without separation. Some clauses restate schema facts (50 per call, cursor repetition), and the density makes it harder to scan than it needs to be.

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 11 optional parameters, no output schema, and a batch-processing loop, this tool could easily be misused; the description covers mode semantics, filter combination, pagination protocol, publication-state side effects, and the returned ok/failed payload. An agent has enough to call it correctly on the first attempt.

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 genuinely adds semantics: it defines the interaction between "mode" and "folders", explains that scope "all" combines folder/type/q2/state filters minus "exclude", and instructs that "nextCursor" is passed as "before". It does not explain every parameter (e.g. "length" is only echoed), keeping it from a 5.

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?

Opens with a specific verb and resource: put games into lists of the current user, take them out, or move them. It clarifies the domain ("the Lists of My games") and maps itself to the underlying REST action, so an agent knows exactly what operation this is. It does not explicitly contrast itself with sibling tools such as set_activity_audience or update_activity_settings, so it stops short of a 5.

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?

Explicitly enumerates the three modes and their conditions: "add" keeps existing memberships, "remove" drops them, "set" makes the game appear in exactly the given folders, including the empty-list edge case. It spells out two valid ways to move a game and explains when to use ids versus scope "all", plus how to iterate batches. This is essentially a usage manual, not just a description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources