Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_franchises

Retrieve Box Office Mojo franchise rankings with release counts and lifetime grosses; sort by total gross, release count, or gross to date in ascending or descending order.

Instructions

Box Office Mojo franchise chart. Returns Box Office Mojo's franchise chart, ranked, with each franchise'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

B3.4/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 usefully discloses the return shape (name, id, path, url, release count, lifetime gross) and the non-obvious detail that sort/sortDir are echoed back only when applied. It says nothing about rate limits, pagination, or how many franchises are returned, but for a read-only chart the gaps are moderate.

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 sentences, front-loaded with what the tool is, then the return fields, then the parameter behavior. Dense but no wasted sentences; only slight compression of the output-field list.

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?

No output schema and no annotations, so the description must supply the return structure, which it does thoroughly (including distinguishing `lifetime_gross` from `lifetime_gross_raw`). For a no-required-parameter read chart this is nearly complete; only list size/pagination is unaddressed.

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 restates the enum values but adds genuine meaning by defining the effect (reordering) and the conditional echo behavior of the two parameters, which the schema does not convey.

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 Box Office Mojo's ranked franchise chart and enumerates the returned fields. It's clear what the tool does, but it does not distinguish itself from the near-identical sibling `boxofficemojo_franchise` (singular), leaving an agent to guess which to use.

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?

No when-to-use, when-not-to-use, or alternative guidance. The description explains how to reorder results but never says when this chart tool is appropriate versus the singular franchise tool or other Box Office Mojo endpoints.

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