Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_brand

Retrieve a brand's box office release records from Box Office Mojo by ID, path, or URL. Returns normalized rows with sorting and pagination for analysis.

Instructions

Box Office Mojo brand detail. Returns normalized release rows from a public Box Office Mojo brand page. Pass exactly one of id, path, or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBox Office Mojo brand id
urlNoAbsolute https://www.boxofficemojo.com brand URL
pathNoBox Office Mojo brand path
sortNoSort field
offsetNoRow offset for pagination (page size 100)
sortDirNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "grossToDate",
+  "maxNumTheaters",
+  "openingWeekendGross",
+  "openingNumTheaters",
+  "releaseDate"
+]
    • addedInput schema / properties / sortDir / enum
      Added value: +[
+  "asc",
+  "desc"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Row offset for pagination (page size 100)",
+  "type": "integer"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Sort field",
+  "type": "string"
+}
    • addedInput schema / properties / sortDir
      Added value: +{
+  "description": "Sort direction",
+  "type": "string"
+}
  3. Addedv1.6.0
  4. Removedv1.6.0
  5. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral transparency burden. It usefully states that the data comes from a public brand page and that the tool returns normalized release rows, implying a read operation. However, it does not disclose potential failure modes, pagination behavior beyond the schema's offset note, or any auth/rate-limit context.

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 concise sentences with no filler. The primary output is stated first, and the critical selector rule is front-loaded in the second sentence. Every word earns its place.

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?

The tool has no output schema, so the description's mention of 'normalized release rows' is valuable for setting return expectations. With 100% schema coverage and the selector constraint clarified, the core calling contract is mostly complete. It lacks sibling differentiation, but the singular 'brand page' resource is reasonably unambiguous.

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. The description adds meaningful value by imposing the exclusivity constraint 'Pass exactly one of `id`, `path`, or `url`,' which is not expressed in the schema's required field list. This resolves a real ambiguity the schema leaves open.

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?

The description identifies a specific verb-resource pair: 'Returns normalized release rows from a public Box Office Mojo brand page.' It is clear about the resource type and output. However, it does not explicitly distinguish itself from sibling tools such as boxofficemojo_brands or boxofficemojo_title.

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

Usage Guidelines2/5

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

The only usage guidance is 'Pass exactly one of id, path, or url,' which addresses parameter selection rather than when to choose this tool over alternatives. There is no statement of when to use this versus boxofficemojo_brands, boxofficemojo_franchise, or boxofficemojo_title, and no exclusions or alternative routing.

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