Skip to main content
Glama
Sign In
Spotify & TMDB Web MCP Server

Spotify & TMDB Web MCP Server

by Chiru144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_actor_tmdb_profile

Read-onlyIdempotent

Fetch an actor's biographical and career profile from TMDB by name to research filmographies and background details.

Instructions

Get rich biographical and career profile details for an actor from TMDB.

Args: actor_name: Name of the actor (e.g. 'Robert Downey Jr.', 'Zendaya')

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": {
      "actor_name": "<actor_name>"
    },
    "name": "get_actor_tmdb_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
actor_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety and network-bound profile is well covered. The description adds only that the data is rich and sourced from TMDB, without covering rate limits, lookup failures, or ambiguity handling. With such rich annotations, a 3 reflects modest added value.

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?

The description is short and front-loaded with the core purpose. The 'Args:' block is somewhat boilerplate, but it adds the only parameter example available given the bare schema.

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 only one required parameter, an output schema present to explain return values, and full annotations covering the read-only/idempotent profile, the description is nearly sufficient. The main missing pieces are ambiguity and failure handling, which are not critical for an agent to invoke the tool.

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 0%, so the description must compensate, and it does partially: the actor_name arg includes concrete examples ('Robert Downey Jr.', 'Zendaya') that clarify expected formatting. However, it adds no further semantics such as exact-match vs fuzzy matching, which matters for a single-parameter lookup tool.

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 ('Get') and a specific resource ('biographical and career profile details for an actor from TMDB'). This clearly separates it from sibling tools like search_actor_movies or create_actor_playlist, though the description itself does not explicitly name those alternatives.

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 or when-not-to-use guidance. The description does not tell an agent whether this should follow search_actor_movies, or what to do when multiple actors share a name.

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

Deploy Server

Other Tools