Skip to main content
Glama
Plex MCP Server

Plex MCP Server

by dustinhansen

Get item

get_item
Read-onlyIdempotent

Retrieve complete metadata for any Plex item by ratingKey, including movie file details, show watch progress, and labels, so you can inspect or verify a media entry.

Instructions

Full metadata for one item by ratingKey (any kind). Movies include file paths/codec/size. Shows include watch progress (episodes watched / total). labels names the item's Plex labels, and is empty when it has none.

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": {
      "ratingKey": "<ratingKey>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing what the payload contains per media type (file paths/codec/size for movies, watch progress for shows) and that labels is empty when unset, which tells the agent how to interpret missing data.

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?

Front-loaded with the core purpose in the first clause, and each following sentence adds distinct information about return shape. The closing clause about labels being empty when absent is slightly awkward but earns its place.

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 single-parameter read tool with full annotations and no output schema, the description covers purpose and the notable variations in returned fields. Minor gaps remain around invalid-key behavior and how to obtain a ratingKey, but nothing essential for a correct call is missing.

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 0%, so the description must carry the meaning; it says the key is a ratingKey and that any item kind is accepted, which is useful. It does not say where ratingKeys come from (e.g., list_media or search results) or address the numeric-only constraint enforced by the schema pattern.

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: full metadata for a single item identified by ratingKey, and explicitly notes it works for 'any kind'. That distinguishes it from lookups like get_children, get_extras, and list_media, though no sibling is named.

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?

Usage is implied by 'one item by ratingKey' – call it when you already have a key and need details – but there is no explicit when/when-not guidance or routing to alternatives such as search or list_media for key discovery.

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