Skip to main content
Glama

List the games of a list

list_folder_activities
Read-onlyIdempotent

List the games inside one list of the current user (the Lists of My games), in the order My games shows them. A list only shows its published games. Same as GET users/{idUser}/activities/?folder= of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response". While "hasMore" is true, pass "nextCursor" as "before" to get the next page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder": "<folder>"
    },
    "name": "list_folder_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
q2NoOnly the games whose title, description or labels contain this text.
sortNoOrder of the games, as in the selector of My games: "updated" (last modified first, the default), "created" (newest first) or "title" (alphabetical).
typeNoOnly the games of this activity type.
beforeNo"nextCursor" of the previous page. Omit it for the first page.
folderYesId of the list, from list_my_folders.
lengthNoGames per page: 20 by default, at most 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description goes well beyond that by disclosing that only published games are returned, that results follow My games ordering, and that the HTTP body or error body arrives wrapped in a "response" field. The hasMore/nextCursor loop is exactly the kind of protocol detail annotations cannot convey.

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?

Three tight sentences, front-loaded with scope, then return shape, then pagination. The REST endpoint reference is a compact way to convey fidelity and return wrapping, though the mid-sentence API path makes the return-body clause slightly harder to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and an unusual response envelope, the description supplies the missing pieces: where results land, how paging terminates, and what is excluded. Coverage is strong; only the absence of any filtering/combination notes (e.g. how q2 interacts with sort) leaves a small gap.

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 adds real meaning by linking the "before" parameter to the response-side "hasMore" flag, which is not present in the schema at all. It otherwise leaves q2, sort, type and length to their already-detailed schema entries.

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?

States a specific verb and resource ("List the games inside one list of the current user") and pins the scope to a single list plus the published-only visibility rule, which functionally separates it from list_my_activities. It does not explicitly name that sibling or contrast the two, so an agent must infer that list_my_activities is the un-foldered alternative.

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?

Gives concrete procedural guidance for the pagination loop ("While hasMore is true, pass nextCursor as before") and a usage-affecting constraint (only published games appear). It stops short of stating when to prefer this over list_my_activities or other list tools, so there is no explicit exclusion.

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