Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_lifetime_grosses

Fetch one page of Box Office Mojo's lifetime gross chart for movies by choosing worldwide or domestic area and a paginated offset, returning ranked titles and grosses as clean JSON.

Instructions

Box Office Mojo lifetime gross chart. Returns one page of Box Office Mojo's lifetime gross chart of movies. area is worldwide (default) or domestic, and offset pages in steps of 200 from 0 to 800. Each row has rank, title, title_id, year and lifetime_gross as an integer, with the displayed text in lifetime_gross_raw.

Input Schema

NameRequiredDescriptionDefault
areaNoChart area. Allowed values: worldwide, domestic
offsetNoChart page offset. Allowed values: 0, 200, 400, 600, 800

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / area / enum
      Added value: +[
+  "worldwide",
+  "domestic"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. Addedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does well: it discloses that the result is a single page (implying pagination is required to iterate), the 0-800 offset range in steps of 200, the default area, and the exact shape of each row including a raw vs integer distinction for lifetime_gross. It does not state rate limits or auth needs, but for a read-only chart listing the disclosure is solid.

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?

Three sentences, front-loaded with the chart identity before parameters and return shape. Slight redundancy in restating 'lifetime gross chart' twice, but every sentence carries content and nothing important is buried.

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, the description compensates by enumerating the returned row fields (rank, title, title_id, year, lifetime_gross, lifetime_gross_raw), which is exactly what an agent needs. Combined with pagination behavior and the area default, the description is essentially complete for this simple 2-parameter read tool.

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 coverage is 100%, so 3 is the baseline, but the description adds value beyond the schema: it gives the default for area (worldwide) which the schema omits, and explains that offset 'pages in steps of 200', clarifying the unit that the schema only lists as bare allowed values.

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 one page of Box Office Mojo's lifetime gross chart of movies.' This clearly identifies the exact chart (lifetime grosses of movies) distinct from siblings like weekend_domestic or year_worldwide. It lacks an explicit sibling call-out, but the resource is unambiguous.

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 establishes when the tool applies implicitly (retrieving a page of the lifetime gross chart) and documents pagination limits, but never says when to prefer it over boxofficemojo_year_worldwide, weekend_domestic, or other chart siblings, nor any exclusion criteria. Usage is inferable but not guided.

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