Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_franchise

Fetch release rows from a Box Office Mojo franchise page by passing one of id, path, or URL; supports sorting and pagination for franchise box office data.

Instructions

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

Input 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

B3.3/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 behavioral burden and does disclose the return content (release rows) and the mutually-exclusive identifier requirement. However, it says nothing about pagination behavior, sort defaults, or what happens if more than one identifier is supplied, so coverage is only partial.

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?

Three short sentences, front-loaded with what the tool is and what it returns, with the identifier constraint last. 'Box Office Mojo franchise detail' is mildly redundant with the name, but the rest earns its place.

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?

For a six-parameter, paginated read tool with no annotations and no output schema, the description is adequate but leaves gaps: pagination via offset/page size, sort/sortDir defaults, and the shape of the returned rows are not addressed. An agent can call it, but not without guessing at paging behavior.

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 baseline is 3, but the description adds a genuinely important constraint the schema omits: the schema lists required as empty, while the description tells the caller exactly one of id/path/url must be provided. That is real semantic value beyond the structured fields.

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?

States a specific verb and resource: it returns release rows from a Box Office Mojo franchise page, which is more than restating the name. It does not, however, distinguish itself explicitly from the sibling boxofficemojo_franchises (list) tool, leaving the singular/plural distinction to be inferred.

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?

There is no guidance on when to use this tool versus boxofficemojo_franchises or boxofficemojo_title; usage is only implied by the word 'detail'. The 'pass exactly one of id, path, or url' line is an invocation constraint rather than a when-to-use rule.

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