Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_franchise

Retrieve Box Office Mojo franchise data by ID, URL, or path. Returns normalized release rows with sortable fields for gross, theaters, opening weekend, and release date.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBox Office Mojo franchise id
urlNoAbsolute https://www.boxofficemojo.com franchise URL
pathNoBox Office Mojo franchise 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, the description carries the full burden. It discloses that the source is a public page and that output is normalized release rows, which hints at a read-only operation. But it does not describe the row structure, error behavior, rate limits, or what happens if more than one identifier is supplied.

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?

Two dense sentences with the core purpose front-loaded and the critical identifier constraint stated immediately after. The opening fragment 'Box Office Mojo franchise detail' is slightly redundant given the tool name, but it still serves as a useful subject line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema covers sort, offset, sortDir, and page size, and the description explains the identifier constraint, so a basic call is well-specified. However, there is no output schema and the description does not describe the fields of the normalized release rows or differentiate this tool from the many boxofficemojo siblings, leaving gaps for an agent.

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 semantics by clarifying that `id`, `path`, and `url` are mutually exclusive alternatives via 'Pass exactly one of...', which is not evident from the schema alone since all parameters are optional.

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 states a specific action and resource: it returns normalized release rows from a public Box Office Mojo franchise page. This is clearly distinguishable from siblings like boxofficemojo_franchises (plural) which presumably lists franchises, but it does not explicitly name any sibling.

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?

It gives an explicit invocation rule: pass exactly one of `id`, `path`, or `url`. However, it does not say when to choose this tool over the many other boxofficemojo_* siblings, such as boxofficemojo_title or boxofficemojo_release_group, nor does it provide exclusions or alternatives.

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