Crawlora MCP

datasets_boxofficemojo_search

Read-only

Search stored theatrical Box Office Mojo title records by title, ID, year, franchise, brand, genre, gross band, or hydration status. Costs 1 credit per record returned (minimum 2), so keep page_size to what you need. Use datasets_boxofficemojo_item for one record or datasets_boxofficemojo_facets to inspect filter values.

Input Schema

Name	Required	Description
`q`	No	Optional full-text query over title and taxonomy names, max 256 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort. Allowed: relevance, worldwide_desc, domestic_desc, peak_worldwide_desc, lifetime_rank_asc, year_desc, year_asc. Defaults to relevance with q, otherwise worldwide_desc.
`year`	No	Optional year that must appear in years_active (worldwide year chart presence).
`brand`	No	Optional brand name filter, max 128 characters.
`genre`	No	Optional genre name filter, max 128 characters.
`hydrated`	No	Optional filter for whether the title page has been hydrated (release groups and market grosses).
`title_id`	No	Optional exact title id filter (IMDb tt… id used by Box Office Mojo), max 32 characters.
`franchise`	No	Optional franchise name filter, max 128 characters.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`gross_band`	No	Optional worldwide gross band. Allowed: under_50m, 50_100m, 100_250m, 250_500m, 500m_1b, over_1b.
`min_domestic`	No	Optional minimum lifetime domestic gross in whole USD dollars.
`lifetime_year`	No	Optional primary lifetime chart year filter.
`max_worldwide`	No	Optional maximum lifetime worldwide gross in whole USD dollars.
`min_worldwide`	No	Optional minimum lifetime worldwide gross in whole USD dollars.
`is_billion_dollar`	No	Optional filter for titles with worldwide gross at least $1B.
`min_foreign_share`	No	Optional minimum foreign share of worldwide gross, 0 through 1.
`max_domestic_share`	No	Optional maximum domestic share of worldwide gross, 0 through 1.
`in_lifetime_top_1000`	No	Optional filter for titles in the lifetime worldwide top 1000 chart.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds a cost model (1 credit per record, minimum 2) and advises trimming page_size, which is real behavioral context not present in structured fields. It stops short of auth or rate-limit detail, so not a full 5.

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?

Three tight sentences, front-loaded with purpose, followed by cost guidance and sibling routing. Every sentence earns its place with no redundancy.

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 an output schema present, return values need no explanation; all 19 parameters are documented in the schema and the description covers the cost model and sibling alternatives. Nothing needed to invoke correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine meaning for page_size by tying it to per-record credit cost, and the enumerated filter list maps onto the filter parameters. Modest but real value beyond the schema.

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 (Search) and resource (stored theatrical Box Office Mojo title records) and enumerates the filter dimensions, letting an agent distinguish it from sibling retrieval tools without opening any schema.

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?

Explicitly routes the agent: use datasets_boxofficemojo_item for a single record and datasets_boxofficemojo_facets to inspect filter values, with the implicit condition that this tool is for multi-record searching. Alternatives and their triggers are named.

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

All Crawlora MCP 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.