Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportingnews_article

Extract title, description, section, authors, timestamps, image, and body paragraphs from a canonical Sporting News US article URL; non-US editions and hub pages are rejected.

Instructions

Get Sporting News article content. Returns a Sporting News US article by canonical url, such as https://www.sportingnews.com/us/nfl/dallas-cowboys/news/<slug>/<id>: title, description, section (the sport or topic in the URL, for example NFL), authors, publication and update times, image and body paragraphs. Tables, embeds, ad slots and related-story lists are excluded. Non-US editions and hub pages are rejected.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Sporting News US article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 discloses returned fields (title, description, section, authors, times, image, paragraphs) and, notably, states what is excluded (tables, embeds, ad slots, related-story lists). It is silent on auth, rate limits, or error behavior, which keeps it short of 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.

Conciseness5/5

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

Front-loaded with purpose, then returned fields, then exclusions/constraints. Three dense sentences with no filler; the reader learns what it does, what it returns, and what it refuses, in that order.

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?

For a single-argument, no-output-schema fetch, the description is complete: it specifies the input format, enumerates the returned content, and rules out the main failure modes (non-US, hub pages). Nothing an agent needs to call it correctly 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 is 3, but the description goes beyond the schema's terse 'Canonical Sporting News US article URL' by spelling out the path shape and giving a full example URL. It also explains the semantics of one returned-derived value (section = sport/topic in the URL, e.g. NFL).

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?

States a specific verb+resource ('Get Sporting News article content') and immediately scopes it as a single article retrieved by canonical URL. It is readily distinguishable from sportingnews_headlines, sportingnews_sections and sportingnews_author siblings without opening any 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?

Explicit input contract: a canonical Sporting News US article URL, with a concrete example and format. It also states that non-US editions and hub pages are rejected, which usefully bounds valid invocation. It stops short of naming alternatives for list-style needs (e.g. sportingnews_headlines), so the when-to-use-vs-sibling guidance is implicit.

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