Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_release

Fetch normalized movie release summaries and domestic daily box office rows from a public Box Office Mojo page by ID, path, or URL.

Instructions

Box Office Mojo release detail. Returns normalized Box Office Mojo release summary fields and domestic daily rows from a public release page. Pass exactly one of id, path, or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBox Office Mojo release id
urlNoAbsolute https://www.boxofficemojo.com release URL
pathNoBox Office Mojo release path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description alone must convey behavioral traits. It states the tool returns data from a public page (indicating a safe read operation) and specifies output as summary fields and daily rows. It does not mention potential errors, rate limits, or authorization needs, but is adequate for a simple retrieval tool.

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 purpose and immediately followed by usage guidance. Every sentence is informative with no wasted words.

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?

Given there is no output schema, the description gives a reasonable idea of what the tool returns ('summary fields and domestic daily rows'). It is complete enough for its complexity, though more detail on output format would be beneficial.

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 description coverage is 100% (all three parameters have descriptions). The description adds the value 'Pass exactly one of `id`, `path`, or `url`', which clarifies the mutual exclusivity but does not explain when to choose one parameter over another. Baseline 3 is appropriate.

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 clearly states the tool returns normalized Box Office Mojo release summary fields and domestic daily rows from a public release page. It uses a specific verb ('returns') and resource ('release'), distinguishing it from sibling tools like boxofficemojo_brand or boxofficemojo_weekend_domestic.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs to 'Pass exactly one of `id`, `path`, or `url`', which is clear guidance on input constraints. However, it does not provide context on when to use this tool versus alternatives, such as when to prefer this over other Box Office Mojo tools like boxofficemojo_title.

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