Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailystaruk_article

Fetch Daily Star (UK) article content from a canonical URL. Returns metadata, section, and body paragraphs while rejecting photo-gallery and sponsored stories.

Instructions

Get Daily Star (UK) article content. Returns public Daily Star (UK) article metadata (including the section) and body paragraphs from a canonical article URL. Photo-gallery and sponsored partner-story URLs are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Daily Star (UK) article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the output (metadata and body paragraphs), the 'public' nature, and URL rejection behavior. However, it does not mention error handling, authentication, or any rate limits, leaving some behavioral transparency gaps.

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?

Two sentences, no fluff, and the main purpose is front-loaded. It conveys purpose, return value, and constraints in a compact structure.

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 simple fetch tool with one well-documented parameter and no output schema, the description adequately covers what is returned and the URL constraints. It could mention error behavior or the exact metadata structure, but those are not critical for basic invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single 'url' parameter, so the schema already documents it. The description adds the rejection of photo-gallery and sponsored partner-story URLs, which is helpful context about the parameter, but does not elaborate on URL format or canonicality beyond that. This meets the baseline of 3.

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 ('Get') and resource ('Daily Star (UK) article content'), and further specifies what is returned (metadata including section, body paragraphs). This clearly differentiates from sibling tools like dailystaruk_headlines or dailystaruk_sections, and also names excluded URL types.

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?

Indicates the tool works from a canonical article URL and explicitly states that photo-gallery and sponsored partner-story URLs are rejected, which guides when to use it. However, it does not explicitly compare to alternative article tools (e.g., dailymail_article) or state when not to use it beyond the URL type constraints.

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