Skip to main content
Glama

Get my status for a title

get_account_states
Read-only

Check if a movie, TV show, or episode is in your TMDB favorites or watchlist, and retrieve your rating for that title.

Instructions

Whether a movie, TV show or episode is in my favorites or watchlist, and my rating for it if I rated it.

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": "get_account_states"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description earns some credit by disclosing the return payload (membership in favorites/watchlist plus the user's rating), which is not in the structured data. It does not say what happens for an unrated or absent title (null vs. empty vs. false), which is the main behavioral ambiguity for a status-lookup tool.

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 compact sentence with no filler; the scope (movie, TV show, episode) and the payload are front-loaded. It loses a point only because the fragmentary phrasing makes the action less immediately scannable than a verb-first sentence would.

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?

With no output schema, the description steps in to state the three things returned (favorites, watchlist, rating), which is the essential missing piece. Conditional episode parameters and ID constraints are fully covered by the schema. The remaining gap is the not-rated/not-present case, which matters when interpreting a 'no' answer.

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%, including the conditional rule that season_number and episode_number are required for episodes, so the schema does the heavy lifting. The description adds no parameter meaning beyond restating the movie/TV/episode scope, 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?

The description names the exact resource and return payload — favorites, watchlist membership, and the user's own rating — for a single movie, TV show, or episode. That is specific enough to distinguish it from generic account tools, but it is written as a noun phrase describing output rather than a verb+resource action, and it never contrasts itself with siblings like get_account_items.

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 at all: nothing says this is the per-title status lookup as opposed to get_account_items (bulk lists) or get_account. No prerequisites (must be authenticated) and no exclusions are stated, so the agent must infer routing from the name alone.

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