Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_genres

Retrieve Box Office Mojo's ranked genre chart with release counts and lifetime grosses; sort results by total gross, title count, or gross-to-date.

Instructions

Box Office Mojo genre chart. Returns Box Office Mojo's genre chart, ranked, with each genre'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, numTitles 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",
+  "numTitles",
+  "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.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds useful behavioral detail ('echoed back only when applied') and fully enumerates the return shape, but never explicitly states this is a read-only operation or covers failure/empty-result behavior.

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?

Front-loaded with the tool's identity, then return fields, then sorting. It is a bit dense and packs the field list into one long clause, but every sentence carries 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?

With no output schema and no annotations, the description compensates well by documenting the return fields and sort echo behavior. The main missing piece is when to prefer it over sibling Mojo endpoints.

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 description coverage is 100%, so the schema already documents both enums; baseline 3 applies. The description adds marginal value by clarifying that the enums correspond to sorting fields/direction and that they are echoed only when applied.

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 ranked genre chart, and it enumerates the returned fields. It is clearly distinct from the many non-Mojo siblings, but it does not explicitly distinguish itself from the singular boxofficemojo_genre tool.

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 alternatives such as boxofficemojo_genre or the other boxofficemojo_* chart endpoints. Sorting behavior is explained, but that is parameter usage, not tool selection guidance.

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