Skip to main content
Glama

list_collection_content_menus

Lists the DLC, expansions, packs, and add-ons attached to a collection copy plus the ones still available to add; read-only.

Instructions

For one copy: DLC/expansions and packs/add-ons you already attached, and the ones you can still add. Read-only. (edit_path is accepted for v1 callers: /users/{u}/collection/{slug}/edit?id=N.)

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

Input Schema

NameRequiredDescriptionDefault
slugNo
edit_pathNo
collection_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • addedInput schema / properties / collection_id
      Added value: +{
      +  "default": "",
      +  "title": "Collection Id",
      +  "type": "string"
      +}
    • addedInput schema / properties / edit_path / default
      Added value: +""
    • addedInput schema / properties / slug
      Added value: +{
      +  "default": "",
      +  "title": "Slug",
      +  "type": "string"
      +}
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 3000,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "edit_path"
      -]
  2. First observedv1.0.1

TDQS

B3/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 behavioral burden. It usefully discloses that the operation is read-only and explains the two content buckets (already attached vs. still addable). However, it does not clarify authentication needs, how the target copy is identified across the three optional parameters, or pagination/response behavior beyond the existence of an output schema.

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?

The description is short and front-loads the content scope with 'For one copy'. The parenthetical about edit_path is relevant but slightly awkwardly appended. Overall it is efficient with little wasted wording.

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?

The tool is a read-only listing operation with an output schema, so return-value details need not be restated. Still, with no annotations and 0% parameter description coverage, the definition should do more to explain how to target a collection copy and how the three optional parameters relate. It is adequate but incomplete for reliable invocation.

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 description must compensate for all three parameters. It explains edit_path in some detail, including the expected path shape for v1 callers, but it leaves slug and collection_id entirely unexplained and does not clarify how to designate 'one copy'. Partial semantic coverage warrants a low score.

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 states the core purpose: listing DLC/expansions and packs/add-ons for 'one copy', split into already attached and still addable content. That gives a clear verb-and-resource scope beyond the name alone. It does not differentiate this tool from nearby siblings such as list_collection_game_options or list_related_content, so it falls 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?

The only usage signal is 'For one copy' and 'Read-only'; there is no explicit guidance on when to choose this tool over alternatives like list_collection_game_options or list_related_content. It also does not explain when to use slug versus collection_id. The edit_path note is compatibility guidance for v1 callers, not selection guidance.

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