Skip to main content
Glama

Top Movies

top_movies
Read-onlyIdempotent

DEPRECATED, Apple discontinued the iTunes movies chart (permanent 404). For popular, trending, or current movies use the tmdb pack instead: tmdb_trending, discover_movie, or get_movie.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "country": "us"
    },
    "name": "top_movies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-100 (default 25)
countryNoISO alpha-2 (default us)

Output Schema

NameRequiredDescriptionDefault
feedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly, idempotent, openWorld, non-destructive, none of which convey that the upstream endpoint is permanently gone. Disclosing the deterministic 404 is the single most valuable behavioral fact here and annotations cannot provide it. It stops short of saying whether a 404 is thrown as an error or an empty result, which is the one remaining operational detail.

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 sentences, deprecation notice front-loaded in caps before any alternatives. Nothing wasted and the priority ordering is exactly right for an agent scanning for viability.

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 deprecated stub with full schema coverage and an output schema, this is complete: an agent knows not to call it, why, and what to call instead. No further information would change the calling decision.

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% (limit 1-100 default 25, country ISO alpha-2 default us), so parameters are already fully documented in the structured data. The description adds nothing about parameters, and given the tool is dead, no parameter guidance is warranted — 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 identifies the resource as the iTunes movies chart and immediately states its status: Apple discontinued it and it returns a permanent 404. It is unambiguous about what the tool was, though it never states the operation itself (listing top movies) in verb form, relying on the title/name for that.

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

Usage Guidelines5/5

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

Gives an explicit when-not-to-use ('DEPRECATED... permanent 404') plus named alternatives for the actual need: tmdb_trending, discover_movie, or get_movie, with the condition 'popular, trending, or current movies'. An agent knows exactly where to route instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.