Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skynews_author

Retrieve a Sky News author's profile from a canonical URL, returning name, job title, biography, recent articles, and contact details.

Instructions

Get a Sky News author profile. Returns a Sky News author's profile by canonical url (https://news.sky.com/author/<name>-<id>): name, job_title, biography paragraphs and recent articles. An info list carries whatever else the page shows, as label and value entries with an optional link, such as expertise, location, social handles or email.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Sky News author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully describes the shape of the response, including the semi-structured `info` list, but says nothing about read-only safety, whether the profile is cached/live, how many "recent articles" are returned, or any pagination 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 core purpose and then the return contract; the `info` list detail is the only slightly verbose part but it is genuinely informative. No filler or restatement of the tool name.

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?

For a single-parameter read tool with no output schema and no annotations, the description compensates well by documenting the return fields and the flexible `info` list. The remaining gap is that cardinality and any access constraints are unstated.

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 already 100% (baseline 3), and the description adds real value beyond it by giving the canonical URL template `https://news.sky.com/author/<name>-<id>`, which tells the agent the expected identifier shape rather than just "Canonical Sky News author URL".

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?

States a specific verb and resource ("Get a Sky News author profile") and enumerates the returned content (name, job_title, biography paragraphs, recent articles, info list). It is clearly distinguishable from sibling article/headline/section tools by the author-profile resource, though it never names a sibling to contrast with.

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: the canonical URL format hints at the required input, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative (e.g. skynews_article for a single story). An agent can infer the case, but nothing is spelled out.

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