Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

cricbuzz_auction_live_blog

Fetches an edition's auction live blog article and returns its public NewsArticle JSON-LD content with linked dynamic tags for the specified tournament and year.

Instructions

Get an edition's auction Live Blog article. Returns the public NewsArticle JSON-LD content and dynamic tags linked from the selected edition's Auction Live Blog tab. Not all editions expose this tab; Cricbuzz may return not found or a page without a NewsArticle. 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

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return payload (public NewsArticle JSON-LD plus dynamic tags) and the two failure modes (not found, or page without a NewsArticle). Missing auth/rate-limit notes keep it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is retrieved, followed by return shape and caveats. No filler; every sentence contributes.

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 exists, so the description must describe returns, and it does (JSON-LD NewsArticle, dynamic tags). It also covers availability caveats. A note on empty/partial result handling would make it fully complete.

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 coverage is 100% and both parameters already document valid values. The description's 'Discover tournament/year from cricbuzz/auction/seasons' mostly repeats what the schema properties already say, adding no format or syntax detail beyond it.

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 — fetching an edition's auction Live Blog article — and scopes it to the Auction Live Blog tab, which distinguishes it from generic auction news/live siblings. It does not name the closest alternative (cricbuzz_auction_live) outright, so it falls short of a 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?

Gives the prerequisite (discover tournament/year from cricbuzz/auction/seasons) and warns that not all editions expose the tab. It does not explicitly state when to prefer this over cricbuzz_auction_news or cricbuzz_auction_live, so no exclusion guidance.

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