Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

boxofficemojo_weekend_domestic

Retrieve domestic weekend box office rankings from Box Office Mojo by specifying a year and week number. Returns normalized data rows.

Instructions

Box Office Mojo domestic weekend box office. Returns normalized rows from Box Office Mojo's public domestic weekend chart. Empty upstream weekend pages return a typed not-found error rather than an empty success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekYesWeekend number, 1 through 53
yearYesDomestic weekend year, from 1982 through 2100
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that empty weekend pages return a typed not-found error rather than empty success, which is helpful. However, it lacks info on auth, rate limits, or whether the data is updated periodically.

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?

Three sentences, no filler. Front-loaded with purpose, then output, then error behavior. Every sentence 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?

Given no output schema, the description could have elaborated on the fields in the normalized rows. It also doesn't mention the year range (1982–2100) which is in schema but not in description. Adequate but has gaps.

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 baseline 3. The description does not add extra meaning beyond what the schema already provides for year and week parameters.

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 it returns normalized rows from Box Office Mojo's public domestic weekend chart, with a specific verb 'returns' and resource. It mentions error handling, but does not explicitly differentiate from sibling tools like boxofficemojo_weekend_domestic_by_distributor or boxofficemojo_weekend_domestic_estimates.

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 guidance on when to use this tool versus siblings. The description does not mention prerequisites, when-not to use, or alternatives. The agent is left to infer from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server