Retrieve recent videos from the public Sky News videos hub. Get structured JSON data for video headlines, links, and publication details.
Get the Sky News videos hub. Returns recent videos from the public Sky News videos hub.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the behavioral disclosure burden. It adds useful context by noting the hub is 'public' and that it 'returns recent videos,' which signals a read operation, but it does not mention pagination, limits, or output structure. Adequate for a simple zero-parameter read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but has some redundancy: 'Get the Sky News videos hub' largely restates the tool name, and all substantive information appears in the second sentence. It is understandable, but not every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter tool with no output schema, the description covers the core purpose and the public nature of the content. It does not clarify the response shape, item count, pagination, or how this differs from the sibling skynews_video tool, leaving some context incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters and schema coverage is 100%, so there are no parameter semantics for the description to clarify. The zero-parameter baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a specific resource ('Sky News videos hub') and a clear action ('Get') plus the result ('returns recent videos'). It is clear about what the tool does, though it does not explicitly contrast with the similarly named sibling skynews_video.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the use case: call this when you want recent public Sky News videos. However, it gives no explicit alternatives, exclusions, or guidance about when to prefer skynews_video or other news tools, so usage guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.