Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_genre

Fetch normalized box office release data for a specific genre from Box Office Mojo by providing its ID, path, or URL.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBox Office Mojo genre id
urlNoAbsolute https://www.boxofficemojo.com genre URL
pathNoBox Office Mojo genre 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns normalized release rows from a public genre page, which is useful, but it does not describe error handling, rate limits, or the structure of the returned rows. The mention of 'public' hints at access level, but depth is limited.

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?

The description is two sentences with no redundancy. It front-loads the purpose and the key constraint, making it easy to parse. Every word 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?

Since there is no output schema, the description should explain the return format more thoroughly. It only says 'normalized release rows' without detailing fields or default behaviors. The schema covers sort and pagination via `sort` and `offset` (with page size noted), but default ordering and row structure are not clarified. For a tool with six parameters and no output schema, this is a moderate completeness level.

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?

The input schema already describes all six parameters at 100% coverage, so the baseline is 3. The description adds valuable meaning beyond the schema by stating that exactly one of `id`, `path`, or `url` must be provided, which is a critical constraint not expressed in the schema. This enhances the agent's ability to invoke the tool correctly.

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?

The description clearly states the tool returns normalized release rows for a Box Office Mojo genre page. It identifies the specific resource (genre) and the action (returns release rows), distinguishing it from sibling tools like boxofficemojo_title or boxofficemojo_release, though it doesn't explicitly name 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?

The description gives a clear parameter constraint ('Pass exactly one of id, path, or url') but does not explain when to use this tool versus alternatives such as boxofficemojo_genres or boxofficemojo_showdown. The context implies usage for genre-specific data, but no explicit exclusions or alternative conditions are provided.

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