Skip to main content
Glama

Delete my rating

delete_rating
DestructiveIdempotent

Remove your rating from a movie, TV show, or TV episode by providing its TMDB ID and media type; include season and episode numbers to target an episode.

Instructions

Remove my rating from a movie, TV show or episode.

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>"
    },
    "name": "delete_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB movie ID, or the TV show ID when media_type is tv or episode
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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description's 'Remove' merely restates that. It adds no operational context such as behavior when no rating exists, authentication requirements for 'my' account scope, or whether season/episode must accompany episode deletions.

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?

A single, front-loaded sentence with no filler or redundancy. Its brevity is appropriate, though the brevity is also where the missing guidance comes from.

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?

With annotations covering the destructive/idempotent profile and a fully documented schema, the core call path is clear. However, for a destructive mutation with no output schema, the description says nothing about failure modes (no rating present, invalid episode pairing) or confirmation of what was removed.

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% and all four parameters, including enum and conditional requirements for season_number/episode_number, are documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Remove') and resource ('my rating') plus the media scope (movie, TV show, episode), so the agent can distinguish it from 'rate' as the inverse operation. It stops short of explicitly naming that sibling or the 'mine-only' constraint's implications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of the alternative 'rate' tool for changing a rating, and no note that the target must already have a rating. The agent must infer usage entirely from the one sentence.

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