Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_genre

Fetch release rows from a Box Office Mojo genre page by ID, path, or URL; supports sorting and pagination for genre box office data.

Instructions

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

Input 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.5/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 does disclose the return shape ('release rows') and the mutual-exclusivity of the three locators, and the word 'Returns' implies a read operation. However, it says nothing about auth needs, rate limits, error behavior when a genre is missing, or pagination semantics beyond the schema's offset field.

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 tight sentences with the purpose front-loaded and the critical input constraint second. No filler, no restatement of the title, nothing that fails to earn its place.

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 six-parameter read tool with no output schema and no annotations, the description covers purpose, return content, and the locator constraint, and the schema covers the remaining parameters including sort, sortDir, and offset. The main gap is that sort/sortDir behavior is not summarized, but overall it is sufficient to invoke correctly.

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, but the description adds a genuine constraint the schema does not encode: the three locators are mutually exclusive and exactly one must be supplied. That is real meaning beyond the flat, all-optional 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 release rows from a Box Office Mojo genre page,' which tells an agent it is a detail/listing fetch for a single genre. The singular 'genre detail' implicitly distinguishes it from the plural boxofficemojo_genres sibling, but the description never names that sibling explicitly, so differentiation is left to inference.

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 when-to-use guidance, no mention of alternatives like boxofficemojo_genres (list) or boxofficemojo_title, and no prerequisites. The only usage instruction is the 'pass exactly one of id, path, or url' constraint, which is invocation mechanics rather than 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