Skip to main content
Glama

Add or remove from watchlist

set_watchlist
DestructiveIdempotent

Add or remove a movie or TV show from a TMDB watchlist by specifying its media type, ID, and watchlist status.

Instructions

Add a movie or TV show to my watchlist (watchlist=true) or remove it (watchlist=false).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_type": "<media_type>",
      "media_id": "<media_id>"
    },
    "name": "set_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYesTMDB movie or TV show ID
watchlistNo
media_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is structured data. The description adds the useful fact that this single tool serves both directions of the operation, but never says whether removal is permanent, whether an existing entry is overwritten, or what authentication/account context is required.

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 sentence that front-loads the primary action and resolves both modes parenthetically. There is no filler, and the boolean mapping is placed where a caller will act on it immediately.

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

Completeness3/5

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

For a three-parameter, no-output-schema tool this covers the mechanics adequately: what it does, and how the boolean selects add versus remove. The remaining material gap is disambiguation from the four or so watchlist-adjacent siblings, plus any note on reversibility of removal, which an agent needs before committing a destructive write.

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 only 33%: media_id carries a description while watchlist and media_type have none. The description compensates by defining the meaning of the watchlist boolean in both states, which is exactly the parameter the schema leaves undocumented; media_type is self-explanatory through its movie/tv enum.

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 and resource ('Add a movie or TV show to my watchlist') and explicitly covers the inverse operation via the watchlist boolean. It does not, however, distinguish this from sibling tools like set_favorite, add_to_list, or remove_from_list, so an agent cannot tell from the text alone why watchlist is the right target rather than a user list or favorites.

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 does give in-tool routing ('watchlist=true' to add, 'watchlist=false' to remove), which resolves the add-vs-remove choice without opening the schema. It offers no guidance on when to use this tool at all versus the many similar siblings (set_favorite, add_to_list, remove_from_list), leaving that selection to inference.

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