Skip to main content
Glama

Delete lists

delete_folders
DestructiveIdempotent

Delete one or several lists of the current user (the Lists of My games). The games inside are not deleted: they stay in My games and in their other lists. Ids of lists of other users are ignored. Same as POST users/{idUser}/folders/ with action=delete of the Educaplay REST API, for the current user: its JSON body, or its error body, comes in "response".

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": {
      "ids": "<ids>"
    },
    "name": "delete_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds of the lists, from list_my_folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description goes further with non-obvious behavior: no cascade deletion of contained games, silent ignoring of foreign list ids, and a note that the raw API JSON or error body is passed back in 'response'. The return statement is somewhat opaque, but it adds real context beyond the annotations.

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?

Front-loaded with the core action, followed by two short clarifying sentences. The final sentence referencing the REST endpoint and the 'response' field is dense and slightly awkward, but it carries information rather than padding.

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?

For a single-parameter destructive tool with no output schema, the description covers scope, non-obvious non-destructive side effects, and return behavior. The explanation of how the API response surfaces in 'response' is imprecise enough that the agent knows something returns but not its structure.

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% and the schema already explains 'Ids of the lists, from list_my_folders.' The description adds a semantic rule not in the schema: ids of other users are silently ignored rather than erroring, which changes how the agent should interpret results.

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 a specific verb and resource ('Delete one or several lists'), scopes it to the current user's own lists, and clarifies the boundary against other destructive operations by noting the games inside survive. An agent can distinguish this from create_folder/rename_folder/list_my_folders without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage context is implied through preconditions: ids must come from list_my_folders, and ids belonging to other users are ignored. There is no explicit when-to-use versus a sibling or when-not guidance, so the agent must infer the call site.

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