Skip to main content
Glama

Add or remove a favorite

set_favorite
DestructiveIdempotent

Add or remove a TMDB movie or TV show from favorites using its media type and ID; set favorite=true to add it or favorite=false to remove it.

Instructions

Mark a movie or TV show as a favorite (favorite=true) or remove it from favorites (favorite=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_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
favoriteNo
media_idYesTMDB movie or TV show ID
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 covered. The description reinforces that removal is a real mutation but adds no new behavioral context such as account scoping, permission requirements, or what the call returns. It does not contradict the annotations.

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 with no filler, front-loading the primary action and folding the boolean semantics into a compact parenthetical. Nothing could be removed without losing meaning.

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 simple three-parameter mutation with no output schema, the description covers the core action and the flag semantics adequately. It omits any note about the account context the favorite attaches to or what a success response looks like, which is a modest but real gap for a destructive operation.

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%, with media_id being the sole documented property, so the description has real work to do. It supplies the missing semantics for the favorite flag (true marks, false removes) and implicitly scopes media_type to movie or TV, which is exactly the gap in the schema.

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?

The description states a specific verb (mark/remove) and resource (favorite) plus the media scope (movie or TV show), so an agent knows exactly what the tool does. It does not explicitly contrast itself with near-neighbors such as set_watchlist or add_to_list, which keeps it 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 parenthetical mapping of favorite=true to 'mark' and favorite=false to 'remove' gives practical guidance for the flag, but it is parameter guidance rather than when-to-use guidance. There is no statement about when to prefer this over set_watchlist or add_to_list, nor any prerequisite or exclusion.

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