Skip to main content
Glama

get_on_deck

Retrieve 'Continue Watching' items from your Plex Media Server using AI-powered natural language queries through the Plex MCP Server.

Instructions

Get on deck (continue watching) items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that fetches 'on deck' (continue watching) items from the Plex API endpoint '/library/onDeck', extracts metadata, and returns a formatted JSON response with relevant fields like ratingKey, title, progress info.
    private async getOnDeck() {
      const data = await this.makeRequest("/library/onDeck");
      const items = data.MediaContainer?.Metadata || [];
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              onDeck: items.map((item: any) => ({
                ratingKey: item.ratingKey,
                title: item.title,
                type: item.type,
                viewOffset: item.viewOffset,
                duration: item.duration,
                lastViewedAt: item.lastViewedAt,
              })),
            }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:88-95 (registration)
    Tool registration in the ListTools response, including name, description, and empty inputSchema (no parameters required).
    {
      name: "get_on_deck",
      description: "Get on deck (continue watching) items",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition: an empty object, indicating the tool takes no parameters.
    inputSchema: {
      type: "object",
      properties: {},
    },
  • src/index.ts:274-275 (registration)
    Dispatch/registration in the CallToolRequestHandler switch statement, mapping the tool name to the getOnDeck handler method.
    case "get_on_deck":
      return await this.getOnDeck();
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves items but doesn't disclose behavioral traits such as whether it requires authentication, how results are ordered or limited, or if it's read-only. The description is minimal and lacks essential context for safe invocation.

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 very concise—a single phrase—and front-loaded with the core purpose. However, it could be more structured or informative without adding unnecessary length, as it currently feels slightly under-specified rather than optimally efficient.

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 the complexity of media retrieval tools and the lack of annotations or output schema, the description is incomplete. It doesn't explain what 'on deck' entails, the format of returned items, or any limitations, making it inadequate for an agent to use the tool effectively without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, earning a baseline score of 4 for adequately handling the lack of parameters.

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

Purpose3/5

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

The description 'Get on deck (continue watching) items' clearly indicates the action (get) and resource (on deck items), but it's somewhat vague about what 'on deck' specifically means. It distinguishes from siblings like 'get_watch_history' or 'get_recently_watched' by focusing on 'continue watching' items, though the distinction could be more explicit.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or compare it to sibling tools like 'get_recently_watched' or 'get_watch_history', leaving the agent to infer usage based on the name alone.

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

Related 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