Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_videos

Fetch Cricbuzz auction video cards for a selected tournament and year, returning video IDs, page URLs, titles, durations, and thumbnails while excluding the global Featured Videos sidebar.

Instructions

Get an edition's Cricbuzz Auction Videos cards. Returns only the selected edition's Auction Videos cards with video IDs, page URLs, titles, durations and thumbnail metadata. The global Featured Videos sidebar is excluded. If Cricbuzz displays No Videos Available, items is an explicit empty array with empty_state=no_videos. Discover tournament/year from cricbuzz/auction/seasons.

Input Schema

NameRequiredDescriptionDefault
yearYesEdition from cricbuzz/auction/seasons: IPL 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026; WPL 2023, 2024, 2025, 2026, 2027; SA20 2027; HUNM 2026; HUNW 2026
tournamentYesTournament identifier from cricbuzz/auction/seasons: ipl, wpl, sa20, hunm, hunw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it enumerates return fields, explicitly excludes the global Featured Videos sidebar, and documents the empty-state contract (explicit empty array with empty_state=no_videos). No info on pagination or rate limits keeps it from 5.

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?

Four tight sentences, front-loaded with purpose, then return shape, then edge case, then prerequisite. Nothing is wasted and each sentence adds distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Only two required params, no annotations and no output schema, so the description must explain returns and edge cases itself — which it does fully (field list plus explicit empty-state behavior). An agent has everything needed to call it correctly.

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 both params (tournament, year) are already well documented with valid values. The description's only added parameter guidance, 'Discover tournament/year from cricbuzz/auction/seasons', largely repeats the schema, so baseline 3 applies.

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?

Specific verb+resource: 'Get an edition's Cricbuzz Auction Videos cards', with a precise scope (one edition, cards with IDs/URLs/titles/durations/thumbnails). It doesn't explicitly contrast with the other video siblings (cricbuzz_video_playlists, cricbuzz_video_categories), so it stops just short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete prerequisite/discovery path ('Discover tournament/year from cricbuzz/auction/seasons'), which tells the agent how to construct valid inputs before calling. It stops short of 5 because it never states when this is the wrong choice versus the other Cricbuzz video tools.

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