Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_video_playlists

Retrieve every Cricbuzz video playlist card with playlist ID, title, count, preview link, and canonical URL for playlist discovery and metadata collection.

Instructions

Discover Cricbuzz video playlists. Returns every playlist card currently linked from the public Playlists page, including its dynamic playlist ID, title, count, preview video link, and canonical URL. The endpoint returns playlist metadata only and does not proxy video assets.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses that results are the playlist cards 'currently linked from the public Playlists page' (i.e. a live, snapshot-in-time index rather than a complete archive) and explicitly bounds expectations with 'returns playlist metadata only and does not proxy video assets.' That prevents the common false assumption that calling it yields playable video data. It stops short of stating pagination or any rate/limit behavior, but for a public read-only index that is a minor gap.

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 sentences, front-loaded with the action and resource, then the return shape, then the scope caveat. Nothing is padded, though the opening 'Discover Cricbuzz video playlists' is largely restated by the following sentence and could be merged with it.

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?

There is no output schema, so the description must carry the return contract — and it does, naming all five fields an agent will receive. Combined with the explicit 'metadata only, no video assets' caveat, an agent has enough to call it and interpret the result. The only unaddressed item is whether the list is paginated or bounded.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter semantics for the description to compensate for. The description correctly implies no input is needed ('returns every playlist card'), matching the schema exactly.

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?

The description pairs a specific verb ('Discover') with a specific resource ('Cricbuzz video playlists') and then enumerates exactly what a card contains (playlist ID, title, count, preview video link, canonical URL). It is clearly distinguishable in substance from siblings like cricbuzz_video_* or cricbuzz_match_* tools, though it never names a sibling to steer against.

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?

Usage is implied rather than stated: calling this returns the current video collections index, which an agent can infer is the right entry point for browsing Cricbuzz video playlists. There is no explicit when-to-use/when-not, no mention of whether a companion tool (e.g. cricbuzz_video_categories) should be used to drill into individual videos, and no prerequisites stated.

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