Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_goofs

Find IMDb-listed goofs for a movie or TV title using its ID or URL. Returns facts with spoiler flags, categories, and total count.

Instructions

IMDb title goofs. Returns the goofs IMDb lists for a title. Pass exactly one of id or url. Each entry in facts has the text, a spoiler flag and, when IMDb groups it, a category such as Continuity. total is the count IMDb lists and has_more is true when only part is returned.

Input Schema

NameRequiredDescriptionDefault
idNoIMDb title id
urlNoAbsolute https://www.imdb.com/title/<id>/ URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose the return shape: `facts` entries with text, a `spoiler` flag and an optional category, plus `total` and `has_more`. It does not state that the call is read-only or how to page for the missing entries when `has_more` is true, which is a meaningful gap.

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?

Six tight sentences, front-loaded with what the tool returns before the parameter constraint and the field breakdown. No filler, though the field-list sentence is dense enough to slow a quick scan.

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?

There is no output schema and no annotations, so the description must describe the payload, and it does so at field level (`facts`, `spoiler`, category, `total`, `has_more`). Only the pagination path for partial results is left unexplained.

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?

Schema coverage is 100%, so the schema already documents both parameters; baseline is 3. The description adds real meaning by asserting the mutual-exclusivity constraint ("exactly one of `id` or `url`"), which the schema itself does not encode.

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 and resource: "Returns the goofs IMDb lists for a title." It is clearly distinguishable from data-adjacent siblings like imdb_title_trivia or imdb_title_quotes, but it never names an alternative, so differentiation is inferential rather than explicit.

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?

"Pass exactly one of `id` or `url`" is a parameter-acceptance rule, not selection guidance. It never says when to reach for this tool versus imdb_title_trivia or other title sub-resources, so usage is only implied by the resource 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