Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skynews_videos

Lists recent Sky News videos from the videos hub, returning title, URL, summary, author, lead image, publication time, and type; use each URL for detailed metadata.

Instructions

Get the Sky News videos hub. Lists recent videos from the Sky News videos hub. Takes no parameters. Each item has its title, URL, summary, author, lead image, publication time and type. An item's url can be passed to skynews-video to get that video's own metadata.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 disclose the key behavioral facts: it takes no parameters, returns a list of recent videos, and enumerates the item fields (title, URL, summary, author, lead image, publication time, type). It does not discuss pagination or rate limits, but for a read-only listing this is solid coverage.

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?

Front-loaded with the purpose and organized logically (what it is, no params, item shape, follow-up tool). The opening two sentences overlap slightly ("Get the hub" / "Lists recent videos from the hub"), a minor redundancy in an otherwise tight description.

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 appropriately compensates by describing the item fields and the downstream relationship to skynews-video. Complete enough for an agent to call and use the result, with only pagination/limits left unspecified.

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?

Zero parameters, so the baseline is 4. The description reinforces this with "Takes no parameters," removing any ambiguity about required inputs.

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 and resource ("Get the Sky News videos hub. Lists recent videos...") and explicitly differentiates from the sibling skynews-video by explaining the item `url` can be passed to it for per-video metadata. An agent can distinguish this listing tool from the detail tool without opening either 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?

The description makes clear this is a parameterless hub listing and names the follow-up tool (skynews-video) for drilling into a specific video, giving useful workflow context. It stops short of stating when NOT to use it (e.g., vs skynews_headlines or skynews_news), so no explicit exclusions.

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