Studio Ghibli

Films

films

Read-onlyIdempotent

List all Studio Ghibli films (up to optional limit), returning title, director, producer, release year, running time, Rotten Tomatoes score, and related character/location/vehicle URLs.

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`count`	Yes	Number of items returned.
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10
+  },
+  {}
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Film description",
+            "type": "string"
+          },
+          "director": {
+            "description": "Film director name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Film unique identifier",
+            "type": "string"
+          },
+          "locations": {
+            "description": "Array of location IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "original_title": {
+            "description": "Original Japanese title",
+            "type": "string"
+          },
+          "original_title_romanised": {
+            "description": "Romanized original title",
+            "type": "string"
+          },
+          "people": {
+            "description": "Array of people IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "producer": {
+            "description": "Film producer name",
+            "type": "string"
+          },
+          "release_date": {
+            "description": "Release date",
+            "type": "string"
+          },
+          "rt_score": {
+            "description": "Rotten Tomatoes score",
+            "type": "string"
+          },
+          "running_time": {
+            "description": "Running time in minutes",
+            "type": "string"
+          },
+          "species": {
+            "description": "Array of species IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Film title",
+            "type": "string"
+          },
+          "url": {
+            "description": "API URL for this film",
+            "type": "string"
+          },
+          "vehicles": {
+            "description": "Array of vehicle IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 16, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds return fields and the optional limit but does not disclose potential performance characteristics, pagination, or other behavioral traits 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?

The description is a single sentence, front-loaded with the action 'List', and includes all necessary details without redundant or filler content.

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?

The tool is simple with one optional parameter, has an output schema, and rich annotations. The description covers the core purpose, return fields, and limit semantics, which is sufficient for a read-only listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter 'limit' with no description (0% coverage). The description compensates by stating 'up to optional limit', clarifying it as a maximum count. This adds meaning beyond the bare schema, though it doesn't specify defaults or maximum values.

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 uses the specific verb 'List' and clearly identifies the resource as 'all Studio Ghibli films' with an optional limit. This distinguishes it well from siblings like 'film', which likely targets an individual film.

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 usage for listing films but does not explicitly contrast it with alternatives like 'film' or provide when-not-to-use guidance. The 'optional limit' gives some context but no clear decision guidance.

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

All Studio Ghibli tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.