Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boxofficemojo_release_group

Fetch market release rows grouped by region from a Box Office Mojo release-group page by passing an id, path, or URL.

Instructions

Box Office Mojo release group detail. Returns market release rows grouped by region from a Box Office Mojo release-group page. Pass exactly one of id, path, or url.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. 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 behavioral burden. It discloses the return content (release rows grouped by region), which is useful, but says nothing about permissions, pagination, or rate limits. Partial behavioral disclosure only.

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, front-loaded with the resource and return shape, followed by the parameter constraint. No filler.

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?

No output schema and no annotations, but the description covers what is returned and the key parameter constraint. It is reasonably complete for a read-only data-fetch tool, missing only auxiliary traits like pagination or auth.

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 baseline is 3. The description adds genuine value by stating the mutual-exclusivity constraint ('exactly one of id, path, or url'), which the schema does not encode (all three are optional with no oneOf). This is meaningful semantics beyond the 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 market release rows grouped by region from a Box Office Mojo release-group page. This distinguishes it from generic listing tools, though it does not explicitly contrast with the sibling boxofficemojo_release.

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?

The only guidance is a parameter-selection rule ('Pass exactly one of id, path, or url'), which is not the same as when-to-use guidance. There is no statement of when this tool is appropriate versus boxofficemojo_release or other Box Office Mojo siblings.

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