Skip to main content
Glama

Rate a title

rate
DestructiveIdempotent

Assign a 0.5–10 score to a movie, TV show, or episode on your TMDB account, replacing any previous score.

Instructions

Rate a movie, TV show or episode on my account, from 0.5 to 10 in steps of 0.5. Replaces any earlier rating.

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>",
      "id": "<id>",
      "value": "<value>"
    },
    "name": "rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB movie ID, or the TV show ID when media_type is tv or episode
valueYesRating from 0.5 to 10, in steps of 0.5
media_typeYesmovie, tv for a whole show, or episode for a single TV episode
season_numberNoSeason number. Required when media_type is episode.
episode_numberNoEpisode number. Required when media_type is episode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful behavioral context by stating that the operation replaces any earlier rating and applies to the user's account, though it does not discuss authentication requirements or response behavior.

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?

The description is two concise sentences with the core action and overwrite behavior front-loaded. Every sentence contributes useful information without unnecessary wording.

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 mutation tool with full schema coverage and annotations covering safety and idempotency, the description is largely complete. It could mention episode-specific parameter requirements, but the schema already covers those details and no output schema exists.

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 documents all five parameters. The description repeats the rating range and media types but does not add meaning beyond the schema, such as clarifying season_number and episode_number requirements for episodes.

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 and resource: rate a movie, TV show, or episode on the user's account. It also clarifies overwrite behavior with "Replaces any earlier rating," which helps distinguish it from delete_rating.

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?

Usage is implied by the verb and scope, but the description does not explicitly say when to use this tool versus alternatives such as delete_rating or set_favorite. It gives enough context to infer the primary use case but lacks explicit exclusions or alternative routing.

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