Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_news_story

Fetch a public Cricbuzz news article from its canonical story URL and return JSON-LD headline, author, dates, body, inline links, and series/team/topic tags.

Instructions

Get a public Cricbuzz NewsArticle and its tags. Fetches one public canonical Cricbuzz story URL and returns its JSON-LD headline, author, dates, body, inline links and typed series/team/topic tags. Pass a URL returned by cricbuzz_auction_news or another public Cricbuzz news page. Only https://www.cricbuzz.com/cricket-news/{numeric_id}/{slug} is accepted; premium or login-gated content is not unlocked.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical public Cricbuzz story URL: https://www.cricbuzz.com/cricket-news/{numeric_id}/{slug}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting: it discloses the URL pattern accepted, that only canonical public pages work, and that premium/login-gated content is not unlocked. That is strong context, though it stops short of stating explicit read-only vs. auth characteristics or failure behavior.

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 purpose, then the neighborhood of possible URLs, then the hard acceptance constraint. Slightly dense but every sentence contributes a distinct fact.

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?

With no output schema, the description fully lists the return fields and their nature (JSON-LD, typed tags), and it makes the input constraint explicit. Nothing an agent needs in order to call and interpret the result is missing.

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 the baseline would be 3; the description adds value by specifying the exact accepted pattern (https://www.cricbuzz.com/cricket-news/{numeric_id}/{slug}) and where the URL should come from. That goes beyond the schema's own description of the field.

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 opens with a specific verb+resource ('Get a public Cricbuzz NewsArticle and its tags') and then enumerates the returned fields (headline, author, dates, body, inline links, typed tags). An agent can tell this apart from the sibling list/auction tools without opening the schema.

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 states when to reach for it ('Pass a URL returned by cricbuzz_auction_news or another public Cricbuzz news page') and names an upstream producer of the URL. It does not discuss an alternative for premium content beyond noting that gated content is not unlocked, leaving a small gap.

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