Skip to main content
Glama

Get item details

get_details
Read-onlyIdempotent

Get FULL details of an item FROM THE USER'S COLLECTION including AI analysis, user notes, rating, timeline, and all metadata. For albums: includes track list with durations. For box sets: lists ALL contained albums. Use this to answer specific questions about items the user owns.

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": {
      "media_type": "<media_type>"
    },
    "name": "get_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe title to look up (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
media_typeYesType of media

Output Schema

NameRequiredDescriptionDefault
idYes
yearNo
titleYes
artistNo
genresNo
ratingNo
statusNo
themesNo
tracksNo
creatorNo
summaryNo
trailerNo
cover_urlNo
media_typeYes
user_notesNo
status_labelNo
claude_summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
    • changedOutput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
    • changedOutput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Changed5 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
      +  "description": "Library item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.",
      +  "type": "string"
      +}
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • changedInput schema / properties / title / description
      Previous value: -"The title to look up (partial match supported)"New value: +"The title to look up (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • changedInput schema / required
      Previous value: -[
      -  "media_type",
      -  "title"
      -]New value: +[
      +  "media_type"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Full detail for one item in the user's library, including AI analysis.",
      +  "properties": {
      +    "artist": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "claude_summary": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "cover_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "creator": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "genres": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "media_type": {
      +      "enum": [
      +        "book",
      +        "movie",
      +        "album",
      +        "show",
      +        "anime",
      +        "podcast",
      +        "game",
      +        "manga"
      +      ],
      +      "type": "string"
      +    },
      +    "rating": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status_label": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "summary": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "themes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "tracks": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "duration_ms": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "preview_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "track_number": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "title"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "trailer": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "title": {
      +          "type": "string"
      +        },
      +        "videoId": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "user_notes": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "year": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "title",
      +    "media_type"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: it is scoped strictly to the user's own collection and returns media-specific shapes (track lists with durations for albums, all contained albums for box sets). It does not say what happens when an item is absent from the collection.

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 purpose and scope are front-loaded in the first sentence, and each following sentence adds a distinct fact (album tracks, box set contents, intended use). Capitalized emphasis on FULL and ALL is slightly noisy but not wasteful.

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 an output schema present, return values need no explanation, and the description still covers scope, per-media-type richness, and intended use. It is complete enough to call correctly, with only the not-found/empty case left unaddressed.

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 description coverage is 100%, so the title/item_id/media_type semantics and the id-wins-over-title rule are already fully documented. The description adds only indirect meaning through the media-type-specific return notes, not per-parameter detail, which matches the baseline for fully covered schemas.

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 uses a specific verb and resource ('Get FULL details of an item') and enumerates the payload (AI analysis, notes, rating, timeline, metadata), plus per-type variations for albums and box sets. The emphasis on 'FROM THE USER'S COLLECTION' implicitly separates it from catalog-style siblings like lookup_item, though no sibling is named outright.

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

Usage Guidelines4/5

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

'Use this to answer specific questions about items the user owns' gives a clear positive trigger tied to ownership scope. It stops short of stating when not to use it or naming an alternative such as lookup_item for items outside the collection.

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