Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_brands

Retrieve Box Office Mojo's brand chart ranked by release count or lifetime gross. Sort results by total gross, number of releases, or gross to date to compare film franchises.

Instructions

Box Office Mojo brand chart. Returns Box Office Mojo's brand chart, ranked, with each brand's name, id, path, url, release count and lifetime gross (an integer in lifetime_gross, the displayed text in lifetime_gross_raw). Reorder with sort (totalGross, numReleases or grossToDate) and sortDir (asc or desc); they are echoed back only when applied.

Input Schema

NameRequiredDescriptionDefault
sortNoSort field
sortDirNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "totalGross",
+  "numReleases",
+  "grossToDate"
+]
    • addedInput schema / properties / sortDir / enum
      Added value: +[
+  "asc",
+  "desc"
+]
  2. Changed2 schema fields changed
    • 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.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the returned fields plus the important behavior that sort parameters are echoed back only when applied. It does not mention permissions or rate limits, but for a read-only chart this is reasonably transparent.

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?

Two sentences with no filler, front-loaded with the tool purpose and followed by return fields and sorting controls. Every sentence contributes useful information.

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?

For a two-optional-parameter chart tool with no output schema, the description sufficiently explains return fields and sorting behavior. Minor missing context is whether the chart is paginated or covers all brands, but overall it is complete enough to invoke correctly.

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 coverage is 100% and both parameters are enums already documented in the schema. The description repeats the allowed sort values and adds only the echo-back behavior, so it meets the baseline but does not add much parameter meaning beyond 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 verb and resource: returns Box Office Mojo's brand chart, ranked, with named fields. It is distinguishable from the singular boxofficemojo_brand detail tool, though it does not explicitly name sibling alternatives.

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?

Usage is implied by the chart purpose, but there is no explicit when-to-use guidance, no when-not-to-use conditions, and no comparison to sibling tools such as boxofficemojo_brand or boxofficemojo_franchises.

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