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.

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. 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"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real context about what is returned (AI analysis, notes, ratings, timeline, track lists with durations, box-set album expansion). It doesn't mention cost/rate limits or payload size for large box sets, which keeps it below a 5.

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?

Three short sentences, front-loaded with the core purpose and the scope qualifier before the per-media-type specifics. The capitalized emphasis (FULL, ALL) is slightly noisy but functional rather than 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?

For a read-only detail fetch with a full-coverage schema and an output schema, this covers purpose, scope, and notable return shapes adequately. The only gap is routing versus the near-duplicate siblings (lookup_item, show_item), which the agent must resolve on its own.

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 100% and every parameter is documented in the schema, including the item_id-overrides-title precedence and the ambiguous-partial-match behavior, so the description needn't compensate. Beyond media-type-specific output shapes (albums, box sets), it adds no parameter semantics of its own.

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 ('Get FULL details of an item FROM THE USER'S COLLECTION') and scopes it to owned items, which separates it from search-type siblings. It does not distinguish itself from close neighbors like lookup_item or show_item, so an agent still has to guess among detail-oriented tools.

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 closing sentence ('Use this to answer specific questions about items the user owns') gives a usage context, and 'FROM THE USER'S COLLECTION' implies a precondition the item must already exist. However, there is no explicit when-not guidance or named alternative for lookup_item, show_item, or search_library.

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