Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_release

Fetch Box Office Mojo release details, including summary fields and domestic daily rows, using exactly one release ID, path, or URL.

Instructions

Box Office Mojo release detail. Returns Box Office Mojo release summary fields and domestic daily rows from a release page. Pass exactly one of id, path, or url.

Input Schema

NameRequiredDescriptionDefault
idNoBox Office Mojo release id
urlNoAbsolute https://www.boxofficemojo.com release URL
pathNoBox Office Mojo release path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.1.0

TDQS

A3.7/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 discloses the return content (summary fields plus domestic daily rows), which implies a read-only scrape, but says nothing about auth requirements, rate limits, pagination, or failure modes for an invalid identifier.

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 tight sentences with the resource named first, the return shape second, and the input constraint last. No filler or redundancy.

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 reasonably covers the resource and return shape, and supplies the input exclusivity rule. It is largely sufficient for calling the tool correctly, missing only error/auth behavior.

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 the schema already defines each parameter. The description adds genuinely useful semantics by stating the three parameters are mutually exclusive and exactly one is required, a constraint the schema (all-optional, no oneOf) does not express.

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 resource ('Box Office Mojo release detail') and what is returned (release summary fields plus domestic daily rows from a release page). This distinguishes it from list-type siblings, though it does not explicitly contrast with boxofficemojo_title, which an agent might confuse it with.

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 parameter-selection rule ('pass exactly one of id, path, or url') but no when-to-use or when-not-to-use guidance relative to alternatives like boxofficemojo_title or the weekend/year box office tools. Usage is only implied by the resource name.

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