Skip to main content
Glama
HoneyBearTech

plex-director-mcp

by HoneyBearTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_actor_filmography

Resolve an actor's official filmography, filtering out talk shows and uncredited roles, to see which of their movies are owned or missing in Plex.

Instructions

Resolves an actor's name to their official TMDb filmography, filtering out talk shows, self-appearances, and uncredited roles. When Plex is configured, marks which of those movies the user already has in their Plex library and which they don't. Use this to answer which of an actor's movies the user is missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showNoOnly titles the user has in Plex ('owned'), only those they don't ('missing'), or both (default).
limitNoHow many titles to list, newest first (default 15).
yearToNoOnly titles released in or before this year.
libraryNoJudge ownership only against Plex libraries whose name contains this text, e.g. '4k': 'owned' then means held in a 4K library and 'missing' means not held in any.
yearFromNoOnly titles released in or after this year.
actorNameYesThe exact name of the actor (e.g., 'Harrison Ford').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.0
    • addedInput schema / properties / library
      Added value: +{
+  "description": "Judge ownership only against Plex libraries whose name contains this text, e.g. '4k': 'owned' then means held in a 4K library and 'missing' means not held in any.",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many titles to list, newest first (default 15).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / show
      Added value: +{
+  "description": "Only titles the user has in Plex ('owned'), only those they don't ('missing'), or both (default).",
+  "enum": [
+    "all",
+    "owned",
+    "missing"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / yearFrom
      Added value: +{
+  "description": "Only titles released in or after this year.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / yearTo
      Added value: +{
+  "description": "Only titles released in or before this year.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by revealing the external TMDb source, the filtering of talk shows/self-appearances/uncredited roles, and the conditional Plex ownership marking. It does not cover edge cases like unknown actor names or what happens when Plex is not configured, but the core behavior is honestly and usefully described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences accomplish a lot: the first states the operation, source, and filters, and the second adds the Plex-dependent output and the intended use case. There is no repetition, filler, or unnecessary detail.

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?

Given the tool has six parameters, 100% schema coverage, no annotations, and no output schema, the description provides enough context for normal use: what the tool returns conceptually, what it filters, and when Plex data is included. It could add more edge-case transparency, but nothing essential is missing for selecting and invoking the tool correctly.

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 explains all six parameters, including enums, defaults, ranges, and the subsetting behavior of 'show'. The description adds only a general link to actorName and the owned/missing idea, not much additional meaning. Baseline 3 is appropriate because the description does not need to compensate for schema gaps.

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 states a specific verb ('resolves') and a clear resource ('actor's name to their official TMDb filmography'), then adds concrete scope by naming what is filtered out. The mention of marking Plex ownership and answering which movies the user is missing distinguishes it clearly from sibling tools like search_plex_library or check_movie_status.

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?

The description explicitly says 'Use this to answer which of an actor's movies the user is missing,' which gives a direct use case. It also conditions the Plex ownership behavior on Plex being configured. However, it does not name alternative tools or state when not to use it, so it stops short of full routing guidance.

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

Deploy Server

Other Tools