Skip to main content
Glama

Watchmode

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Title Search

title_search
Read-onlyIdempotent

Search Watchmode for movies and TV shows by name (or IMDb/TMDb ID via search_field); optionally filter by type (movie, tv_series, etc.). Returns Watchmode title IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNo
search_fieldNoWhat search_value IS. Defaults to "name". Watchmode REQUIRES this and rejects anything outside the list — notably "title" is not valid.
search_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "search_value": "Breaking Bad"
-  },
-  {
-    "search_field": "title",
-    "search_value": "Inception",
-    "types": "movie"
-  }
-]New value: +[
+  {
+    "search_field": "name",
+    "search_value": "Breaking Bad"
+  },
+  {
+    "search_field": "name",
+    "search_value": "Inception",
+    "types": "movie"
+  }
+]
    • addedInput schema / properties / search_field / description
      Added value: +"What search_value IS. Defaults to \"name\". Watchmode REQUIRES this and rejects anything outside the list — notably \"title\" is not valid."
    • addedInput schema / properties / search_field / enum
      Added value: +[
+  "name",
+  "imdb_id",
+  "tmdb_tv_id",
+  "tmdb_movie_id",
+  "tmdb_person_id"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "search_value": "Breaking Bad"
+  },
+  {
+    "search_field": "title",
+    "search_value": "Inception",
+    "types": "movie"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Search results for titles from Watchmode API",
+  "type": "object"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the search scope (Watchmode) and that it returns Watchmode title IDs, but discloses nothing about rate limits, result caps, or partial-match behavior — acceptable but not rich.

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?

A single tightly written sentence that front-loads the core action and appends the ID-variant and filter as parentheticals. No filler or redundancy.

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?

Output schema and annotations are present, so return values and safety need not be re-explained. The description still surfaces the returned ID type and covers params, leaving only minor gaps (no pagination/limit behavior) for a search tool.

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 low (33%), so the description must compensate, and it does: it explains search_field is what search_value IS (name vs IMDb/TMDb ID) and that types filters by movie/tv_series. It does not elaborate on the tmdb_person_id case, but the semantics of all three parameters are conveyed.

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 (search) and resource (Watchmode movies and TV shows), and clarifies the ID-lookup variant via search_field. It does not explicitly differentiate itself from siblings like list_titles or title_detail, so it stops short of a 5.

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 implies usage (searching by name when you know the title) and notes the optional type filter, but gives no explicit when-to-use/when-not guidance or routing to alternatives such as list_titles. Usage is inferable rather than stated.

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

All Watchmode toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources