Skip to main content
Glama

Get genres

get_genres
Read-only

Retrieve official movie or TV genre IDs for use in TMDB discover filters. Specify media type and optional language to get the correct genre list for your query.

Instructions

The official genre list with IDs for movies or TV, for use with discover filters.

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

Input Schema

NameRequiredDescriptionDefault
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 safety is covered. The description contributes that the list is 'official' and that entries carry IDs usable as filter values, which is useful content context. It adds nothing about stability/caching of genres, auth requirements, or response shape beyond what annotations and schema imply.

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?

A single sentence with no filler, front-loading what the tool returns (official genre list with IDs) before its purpose. Every clause earns its place.

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 two-parameter read with no output schema, the description covers the returned content and the media_type dimension, and annotations cover safety. The only omission is any mention of the language parameter's effect, which the schema already handles.

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 50%: the language parameter is fully documented in the schema, while media_type has only an enum and no description. The phrase 'for movies or TV' supplies meaning for media_type, closing that gap, but language is never mentioned in the description. Baseline 3 is appropriate.

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 a specific resource (the official genre list with IDs) and scopes it to 'movies or TV', so an agent knows it returns genre identifiers for one media type. It also signals downstream relevance to discover filters, which separates it from the bulk of the sibling read tools. It stops short of explicitly naming discover_movies/discover_tv as the consumers.

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

Usage Guidelines4/5

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

'For use with discover filters' gives clear context for when to reach for this tool: to resolve genre names into IDs before calling a discover endpoint. There are no exclusions or named alternatives, so it falls just short of full when/when-not guidance.

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