Skip to main content
Glama

create_list

Create a custom game list with titles, descriptions, game slugs, and optional ranked, spoiler, or mature-content settings; save it as a draft or publish it publicly.

Instructions

Create a custom game list. games: comma-separated game slugs or a JSON array. Saved as a draft unless publish=true (public).

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": {
      "title": "<title>"
    },
    "name": "create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
gamesNo
titleYes
rankedNo
publishNo
spoilersNo
descriptionNo
mature_contentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose one key non-obvious trait: the list is saved as a draft unless publish=true, and that flag makes it public. It omits other relevant behavior: required permissions, whether titles must be unique, validation/failure behavior, and what happens to the other flags by default.

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?

Two compact sentences with the purpose front-loaded, then format and the draft/publish rule. Nothing is wasted, though the parameter detail is packed into a single semicolon-free run-on clause that reads slightly dense.

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

Completeness2/5

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

For a 7-parameter mutation tool with no annotations and 0% schema coverage, the description covers only a fraction of the surface. An output schema exists so return values needn't be explained, but five of the seven input parameters are opaque.

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 0%, so the description must compensate for all 7 parameters. It explains only two of them: the games format (comma-separated slugs or JSON array) and publish (public vs draft); title, ranked, spoilers, description, and mature_content are left entirely to their bare schema defaults.

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: 'Create a custom game list.' An agent can tell this apart from update_list/delete_list by the verb alone, though the description never names or contrasts those siblings explicitly.

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?

The draft-vs-publish clause implies usage (default is a private draft; publish=true makes it public), but there is no explicit when-to-use guidance, no mention of prerequisites such as authentication, and no routing to update_list for modifying an existing list.

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