Skip to main content
Glama

list_my_lists

Lists your custom game lists with ID, title, published status, game count, and last update time. Use it to review your collections in a read-only view with limit and offset paging.

Instructions

List your custom game lists (id, title, published, number of games, last update). Read-only.

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_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the safety burden and does so with the explicit 'Read-only.' note, which is genuinely useful. It omits ordering of results, pagination behavior, and whether unpublished/private lists are included, which matters given the 'published' field it advertises.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence plus a two-word safety flag, with the resource and returned fields front-loaded and zero filler. Every element earns its place.

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

Completeness3/5

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

An output schema exists, so the enumerated return fields are redundant rather than necessary, and return values need not be explained. What is missing for a paginated list endpoint is pagination/ordering semantics and default behavior, which the schema leaves undefined.

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

Parameters2/5

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

Schema description coverage is 0%, so the two parameters (limit, offset) are documented only by their names and defaults. The description says nothing about them — no page size limits, no max values, no ordering assumption — so it fails to compensate for the coverage gap, though the conventional limit/offset naming limits the damage.

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?

The description names a specific verb+resource pair ('List your custom game lists') and scopes it to the authenticated user's own lists, which separates it from generic siblings like list_wishlist or list_custom_tags. It does not explicitly name a sibling alternative, 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says how this differs from get_list (single list detail) or from other list_* tools, and no note on when pagination matters. Usage is only implied by the resource name.

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