Skip to main content
Glama

Get my favorites, watchlist or ratings

get_account_items
Read-only

Retrieve paginated lists of your favorite, watchlisted, or rated movies and TV shows, with optional sorting, language, and page controls.

Instructions

Paged list of my favorite, watchlisted or rated movies or TV shows. media_type=episode is only valid with kind=rated.

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": {
      "kind": "<kind>",
      "media_type": "<media_type>"
    },
    "name": "get_account_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
pageNoResults page, 1-500. Each page holds up to 20 results.
sort_byNoOrder by when the item was added
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
media_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 adds one genuine behavioral rule the schema does not encode — media_type=episode requires kind=rated — but says nothing about authentication context, result contents, or behavior on empty pages.

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?

Two short sentences, front-loaded with the resource description and followed by the one constraint that matters. No filler or restatement of the title.

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

Completeness5/5

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

For a read-only, non-nested, 5-parameter listing tool with no output schema, the definition plus schema cover scope, pagination size, language default, sort order, and the one invalid input combination. Nothing essential to calling it correctly is missing.

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 60%, and the description contributes the key cross-parameter constraint linking media_type to kind, which the enum alone would let an agent violate. It adds no meaning for page, sort_by, or language, but those are already documented 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?

'Paged list of my favorite, watchlisted or rated movies or TV shows' gives a specific verb (list), resource (account items), and the three modes via kind. It is distinguishable from siblings like get_account_lists or get_account_states, though it never names an alternative explicitly.

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 mention of favorites/watchlist/rated, and the invalid-combination note steers one case, but there is no statement of when to prefer this over set_watchlist, rate, get_account_states, or the discover/search tools.

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