Movies

Search Movies

search_movies

Read-onlyIdempotent

Search for movies by title or keyword. Returns title, director, release date, genre, description, and artwork.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of results to return (1-25, default 10)
`query`	Yes	Movie title or keyword to search for

Output Schema

TableJSON Schema

Name	Required	Description	Default
`movies`	Yes
`total_found`	Yes	Total number of movies found

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "movies": {
+      "items": {
+        "properties": {
+          "artwork_url": {
+            "description": "Artwork image URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Long or short description of the movie",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "director": {
+            "description": "Director or artist name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "genre": {
+            "description": "Primary genre",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "itunes_url": {
+            "description": "iTunes store URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rating": {
+            "description": "Content advisory rating",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "release_date": {
+            "description": "Release date in YYYY-MM-DD format",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "runtime_minutes": {
+            "description": "Runtime in minutes",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Movie title",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "title",
+          "director",
+          "release_date",
+          "genre",
+          "description",
+          "rating",
+          "runtime_minutes",
+          "itunes_url",
+          "artwork_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_found": {
+      "description": "Total number of movies found",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_found",
+    "movies"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Inception"
+  },
+  {
+    "limit": 15,
+    "query": "Christopher Nolan"
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already cover read-only and idempotent behavior. The description adds no extra behavioral context beyond what annotations and schema already provide. It does not contradict the annotations, but also does not contribute meaningful new behavioral details.

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?

The description is two sentences, front-loaded with the tool's primary action, and includes a compact list of return fields. Every sentence is informative with no fluff.

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?

With a low-complexity tool, full schema coverage, and an output schema present, the description adequately covers the necessary context. The return fields listed are redundant with the output schema, but that does not detract from completeness.

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 100%, with clear descriptions for both 'query' and 'limit'. The description's phrase 'by title or keyword' merely restates the query parameter description, adding no new semantic meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Search') and resource ('movies'), and lists return fields. It clearly distinguishes from siblings like search_tv_shows by explicitly scoping to movies.

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?

The description implies when to use the tool (when searching for movies), but it does not explicitly mention alternatives or exclusion criteria. Sibling tools like search_tv_shows are not referenced, so some inference is required.

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

All Movies tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.