Skip to main content
Glama
HoneyBearTech

plex-director-mcp

by HoneyBearTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_actor_filmography

Resolve an actor's name to their official TMDb filmography, filtering out talk shows, news, self-appearances, and uncredited roles, then flag which titles are already in Plex and which are missing.

Instructions

Resolves an actor's name to their official TMDb filmography (movies and TV shows), filtering out talk shows, news, self-appearances, and uncredited roles. When Plex is configured, marks which of those titles the user already has in their Plex library and which they don't. Use this to answer which of an actor's movies or shows the user is missing. Pass mediaType 'movie' when the user asks about movies/films, 'show' for TV/series, and leave it out (any) when the question is about the actor's work in general; keep the same mediaType on follow-ups.

Input 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').
mediaTypeNoOnly movies, only TV shows, or both (default any).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / mediaType
      Added value: +{
+  "description": "Only movies, only TV shows, or both (default any).",
+  "enum": [
+    "movie",
+    "show",
+    "any"
+  ],
+  "type": "string"
+}
  2. 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"
+}
  3. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exclusions (talk shows, news, self-appearances, uncredited roles) and that Plex ownership marking is conditional on Plex being configured. It omits failure modes, rate limits, and permissions, which keeps it short of 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?

Front-loaded with purpose, then filtering, then Plex behavior, then usage guidance. Dense but every sentence is load-bearing; only the mediaType sentence runs slightly long.

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 7-parameter tool with no annotations and no output schema, the description covers intent, filtering, ownership semantics, and the key enum choice. Remaining parameter detail (yearFrom, limit, library, show) is handled by the complete schema, so nothing critical is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by prescribing mediaType values per question phrasing ('movie' for films, 'show' for series, omit for general work) and reinforcing consistency on follow-ups.

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?

States a specific verb and resource ('Resolves an actor's name to their official TMDb filmography') plus the scope (movies and TV shows) and filtering behavior. No sibling tool covers actor filmography, so the agent can place it precisely.

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?

Gives an explicit use case ('answer which of an actor's movies or shows the user is missing') and detailed mediaType selection guidance including follow-up behavior. It does not name a when-not condition or a competing alternative, but its function is fairly unique among siblings.

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