Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_boxofficemojo_item

Retrieve a Box Office Mojo dataset title by IMDb tt ID, returning lifetime grosses, year history, release groups, and market grosses.

Instructions

Get a Box Office Mojo title from the dataset. Returns one Box Office Mojo dataset record by title id (IMDb tt… id used on Box Office Mojo title pages), including lifetime grosses, year history, release groups and market grosses when hydrated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
title_idYesTitle id (IMDb tt… id), e.g. tt0499549

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It accurately describes a read operation ('Get', 'Returns') and adds value by mentioning the 'when hydrated' condition and listing returned data categories (lifetime grosses, year history, etc.). It does not contradict any annotations.

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?

The description is two sentences, front-loaded with the core purpose ('Get a Box Office Mojo title'), and includes necessary detail without padding. Every sentence earns its place, and the structure is easy to scan.

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 simple single-parameter lookup tool with no output schema, the description is reasonably complete. It explains what is returned and the hydration caveat, and the schema covers the parameter. Some ambiguity remains about how to obtain the title_id, but sibling search tools likely provide it.

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?

The schema already provides 100% coverage of the single parameter 'title_id', including an example. The description adds minor context by explaining the id format ('IMDb tt… id used on Box Office Mojo title pages'), but this repeats schema information rather than adding new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Get') and resource ('Box Office Mojo title from the dataset'). It distinguishes from sibling tools by emphasizing it returns a single dataset record by title id, unlike search or facets tools. The included field list further clarifies its scope.

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 implies usage by providing the required parameter (title id) and notes the record includes specific fields when hydrated. However, it does not explicitly state when to use this tool versus alternatives like datasets_boxofficemojo_search or boxofficemojo_title, nor does it mention prerequisites or exclusions.

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