Skip to main content
Glama

get_library_items

Retrieve paginated lists of media items from a Plex library by specifying library key and media type. Control result size and offset to navigate large collections.

Instructions

List items in a library with pagination (useful for large libraries)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
libraryKeyYesLibrary section key
typeNoMedia type (movie, show, episode, artist, album, track)
limitNoNumber of items to return (default: 1000)
offsetNoZero-based offset for pagination (default: 0)
sortNoSort order (optional, e.g., titleSort:asc)

Implementation Reference

  • The PlexTools.getLibraryItems() method - the actual handler that fetches items from a Plex library section with pagination, type filtering, and sorting. It makes a request to /library/sections/{libraryKey}/all and returns a JSON response with items (ratingKey, title, originalTitle, year, type, guid, editionTitle), totalSize, offset, and limit.
    async getLibraryItems(
      libraryKey: string,
      type?: string,
      limit: number = DEFAULT_LIMITS.libraryItems,
      offset: number = 0,
      sort?: string
    ): Promise<MCPResponse> {
      validatePlexId(libraryKey, "libraryKey");
    
      const safeLimit = Number.isFinite(limit) && limit > 0 ? Math.floor(limit) : DEFAULT_LIMITS.libraryItems;
      const safeOffset = Number.isFinite(offset) && offset >= 0 ? Math.floor(offset) : 0;
      const params: Record<string, string | number> = {
        "X-Plex-Container-Start": safeOffset,
        "X-Plex-Container-Size": safeLimit,
      };
    
      if (type) {
        params.type = this.client.getPlexTypeId(type);
      }
      if (sort) {
        params.sort = sort;
      }
    
      const data = await this.client.makeRequest(`/library/sections/${libraryKey}/all`, params);
      const container = data as {
        MediaContainer?: { Metadata?: Record<string, unknown>[]; totalSize?: number };
      };
      const items = container.MediaContainer?.Metadata || [];
    
      return jsonResponse({
        libraryKey,
        offset: safeOffset,
        limit: safeLimit,
        totalSize: container.MediaContainer?.totalSize,
        items: items.map((item) => ({
          ratingKey: item.ratingKey,
          title: item.title,
          originalTitle: item.originalTitle,
          year: item.year,
          type: item.type,
          guid: item.guid,
          editionTitle: item.editionTitle,
        })),
      });
    }
  • The GET_LIBRARY_ITEMS_SCHEMA object defining the tool name ('get_library_items'), description, and input schema with properties: libraryKey (required string), type (enum: movie/show/episode/artist/album/track), limit (number, default 1000), offset (number, default 0), and sort (string).
    const GET_LIBRARY_ITEMS_SCHEMA = {
      name: "get_library_items",
      description: "List items in a library with pagination (useful for large libraries)",
      inputSchema: {
        type: "object" as const,
        properties: {
          libraryKey: { type: "string", description: "Library section key" },
          type: {
            type: "string",
            description: "Media type (movie, show, episode, artist, album, track)",
            enum: ["movie", "show", "episode", "artist", "album", "track"],
          },
          limit: { type: "number", description: "Number of items to return (default: 1000)", default: 1000 },
          offset: { type: "number", description: "Zero-based offset for pagination (default: 0)", default: 0 },
          sort: { type: "string", description: "Sort order (optional, e.g., titleSort:asc)" },
        },
        required: ["libraryKey"],
      },
    };
  • The tool registration in createPlexToolRegistry(), where 'get_library_items' is registered with a handler that calls tools.getLibraryItems() with extracted args (libraryKey, type, limit with default, offset with default, sort).
    registry.register("get_library_items", (args) =>
      tools.getLibraryItems(
        args.libraryKey as string,
        args.type as string | undefined,
        (args.limit as number) || DEFAULT_LIMITS.libraryItems,
        (args.offset as number) || 0,
        args.sort as string | undefined
      )
    );
  • The PLEX_CORE_TOOL_SCHEMAS array that exports GET_LIBRARY_ITEMS_SCHEMA along with other tool schemas for use by MCP servers.
    export const PLEX_CORE_TOOL_SCHEMAS = [
      GET_LIBRARIES_SCHEMA,
      GET_LIBRARY_ITEMS_SCHEMA,
      EXPORT_LIBRARY_SCHEMA,
      SEARCH_MEDIA_SCHEMA,
      GET_RECENTLY_ADDED_SCHEMA,
      GET_ON_DECK_SCHEMA,
      GET_MEDIA_DETAILS_SCHEMA,
      GET_EDITABLE_FIELDS_SCHEMA,
      GET_PLAYLIST_ITEMS_SCHEMA,
      GET_PLAYLISTS_SCHEMA,
      GET_WATCHLIST_SCHEMA,
      GET_RECENTLY_WATCHED_SCHEMA,
      GET_WATCH_HISTORY_SCHEMA,
    ];
Behavior3/5

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

With no annotations, the description must rely on itself. It implies a read operation ('list'), but does not disclose any behavioral traits such as rate limits, caching, or response size limits. The pagination hint is a positive but minimal transparency.

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 a single sentence that front-loads the purpose and key feature (pagination). It is concise and efficient, though it could include a bit more context without losing brevity.

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

Completeness2/5

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

Given there is no output schema and five parameters, the description is minimal. It does not describe return values, error handling, or default behaviors beyond pagination. For a list tool with pagination, more completeness is expected.

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 schema already documents each parameter. The description adds no additional semantic meaning beyond the schema; it only reiterates the pagination concept already captured by limit and offset defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists items in a library and explicitly calls out pagination, which is a key feature. It distinguishes from sibling tools like 'get_libraries' (list libraries) and 'get_media_details' (single item details).

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 description mentions 'useful for large libraries,' hinting at when to use pagination, but lacks explicit guidance on when not to use this tool or how it compares to other list tools on the server. No alternatives or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/niavasha/plex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server