Skip to main content
Glama

List my lists

list_my_folders
Read-onlyIdempotent

List the lists of the current user (the Lists of My games), newest first. Each list brings its number of games ("numResources"), "shareUrl", the public link to share the list, "url", where the user opens it in My games, and "guestAccess", the guests and groups that can open it. Lists cannot contain other lists. Same as GET users/{idUser}/folders/ 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

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": "list_my_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNo"nextCursor" of the previous page. Omit it for the first page.
lengthNoLists per page. Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower; the description still adds real value by enumerating returned fields (numResources, shareUrl, url, guestAccess), noting the API mapping, and stating that body or error body arrives in 'response'. It stops short of covering permissions, rate limits, or error shapes beyond mentioning an error body.

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?

Purpose is front-loaded and the return-field list is informative, but the phrasing is dense and awkward in places ('the Lists of My games', the run-on REST API sentence with 'its JSON body, or its error body, comes in "response"'). The unrelated fact 'Lists cannot contain other lists' is interleaved mid-description.

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 no output schema, the description carries the burden of describing returns and does so field-by-field, and it explains the pagination loop (hasMore/nextCursor). It is nearly complete for a simple read-only list tool, with only permissions and error semantics left thin.

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

Parameters3/5

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

Schema coverage is 100%, so 'before' and 'length' are already documented, giving a baseline of 3. The description adds one genuinely useful link by naming 'nextCursor' as the value to pass as 'before', but does not otherwise extend parameter meaning.

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 lists of the current user') plus scope ('the Lists of My games') and ordering ('newest first'), so an agent knows exactly what is returned. It does not explicitly contrast itself with siblings like list_folder_activities or get_folder_guest_access, which would be needed for 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives such as get_folder_guest_access or list_folder_activities, and no prerequisites or exclusions. The only guidance given is operational (how to page with 'before'), not tool-selection guidance.

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