Skip to main content
Glama

Get movie chart

get_movie_list
Read-only

Retrieve curated movie charts—popular, top-rated, now playing, or upcoming—with optional page, region, and language filters for localized browsing.

Instructions

A curated movie chart: popular, top_rated, now_playing (in theaters) or upcoming.

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": {
      "list": "<list>"
    },
    "name": "get_movie_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes
pageNoResults page, 1-500. Each page holds up to 20 results.
regionNoISO 3166-1 country to localize release dates, e.g. US
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.

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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds only the parenthetical '(in theaters)' for now_playing — no mention of result ordering, page depth, or how region/language change output, leaving the behavioral burden almost entirely on the schema.

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?

One compact sentence with the chart taxonomy front-loaded and no filler. It is efficient, though being a noun phrase rather than a clause makes it slightly less self-evident as a statement of action.

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

Completeness2/5

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

A four-parameter tool with no output schema needs more than a chart taxonomy: nothing explains whether pages are bounded by a total-results limit, whether region affects availability of upcoming titles, or what a returned entry contains. The definition is readable but leaves an agent guessing about call behavior.

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 coverage is 75%: page, region, and language are documented in-schema, and the description supplies the meaning of the undocumented 'list' values (notably now_playing = in theaters). That is real added value, but it stops at labeling the enum and says nothing about how region or language interact with chart results beyond what the schema states.

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 resource concretely — a curated movie chart — and enumerates the four chart types, so an agent knows it retrieves a ranked movie listing rather than a specific movie or an arbitrary list. It does not explicitly separate itself from siblings like get_trending or discover_movies, but the verb+resource pairing is clear.

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 guidance on when to pick this over get_trending, discover_movies, or get_list — all of which plausibly return movie collections. The only routing signal is the enum of chart names, which the agent must infer means 'use this for editorial charts'.

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