Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_parental_guide

Retrieve IMDb parental guide details for a title by ID or URL to check violence, profanity, and frightening scenes with severity ratings and summary counts; spoilers excluded.

Instructions

IMDb title parental guide. Returns the IMDb parental guide for a title. Pass exactly one of id or url. Categories such as violence, profanity and frightening scenes carry a severity of none, mild, moderate or severe and the guide text. A summary gives counts and the highest severity. Spoiler items are excluded.

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

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the return shape (categories with severity levels none/mild/moderate/severe plus guide text, and a summary with counts and highest severity) and an important exclusion ('Spoiler items are excluded'). It stops short of auth, rate-limit or pagination behavior, but the content-level disclosure is substantial and unusually specific.

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?

Front-loaded with the capability statement and then dense, informative sentences about the response. The first two sentences overlap slightly ('IMDb title parental guide' restated as 'Returns the IMDb parental guide for a title'), a minor redundancy in an otherwise waste-free description.

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?

No output schema and no annotations exist, so the description must compensate, and it does by sketching the response structure (categories, severity vocabulary, summary, spoiler exclusion) and the input contract. It is essentially complete for a two-parameter read tool, with only auth/rate-limit context absent.

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 per-parameter definitions already exist, which sets the baseline at 3. The description earns above baseline by adding the mutual-exclusion constraint that the schema does not express (both properties are optional with no oneOf), telling the agent exactly one of `id` or `url` must be supplied.

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?

States a specific verb and resource ('Returns the IMDb parental guide for a title') and names the exact IMDb dataset, which cleanly separates it from sibling IMDb title tools like imdb_title_reviews, imdb_title_quotes and imdb_title_goofs. An agent can identify the tool without opening the schema.

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 only routing-style instruction is the parameter constraint 'Pass exactly one of `id` or `url`', which selects how to call it rather than when to prefer it over an alternative. There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative, so usage is only implied by the name and resource.

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