Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_brand

Fetch release rows from a Box Office Mojo brand page by supplying its id, path, or URL, with optional sorting, sort direction, and pagination.

Instructions

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

Input 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.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the mutually-exclusive selector rule and that the output is release rows, but says nothing about auth requirements, rate limits, error behavior, or what happens when no valid identifier is supplied. Adequate but thin for an un-annotated 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?

Three short sentences, each earning its place: purpose, return content, and the critical selector constraint, front-loaded with no filler.

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?

With no output schema and no annotations, the description should do more heavy lifting. It covers purpose, return shape at a high level, and the identifier rule, but omits format hints for id/path/url, pagination behavior (offset/page size 100), and expected return structure, leaving gaps for a 6-parameter tool.

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, and the description legitimately exceeds it by stating the cross-parameter rule that exactly one of id/path/url must be supplied – a constraint the schema itself does not encode (required is empty). Sort, offset, and sortDir are left to the schema.

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 resource and verb: 'Box Office Mojo brand detail' returning 'release rows from a Box Office Mojo brand page.' This clearly distinguishes it from the sibling list-style tool boxofficemojo_brands, though it never names that sibling explicitly, keeping it from a 5.

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?

The description gives one hard usage constraint ('pass exactly one of id, path, or url') which is genuinely actionable, but offers no guidance on when to choose this tool over boxofficemojo_brands, boxofficemojo_title, or boxofficemojo_franchise. Usage is implied by the resource name rather than stated.

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