Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailymail_article

Retrieve Daily Mail article content from a canonical URL, returning structured JSON with title, authors, publish times, images, paragraphs, and paywall status.

Instructions

Get Daily Mail article content. Returns one Daily Mail article by its canonical url, which must contain an article-<id> path segment. The response has the title, description, publish and update times, section, authors, lead image, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Daily Mail article URL

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 full behavioral burden and does disclose the returned fields, including a `paywalled` flag and body `paragraphs`, which are meaningful behavioral traits for an agent. It omits auth needs, rate limits, and any pagination, so it stops short of full coverage.

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, front-loaded with the action, then the URL format constraint and response shape. Every clause earns its place with no filler.

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-parameter read with no output schema and no annotations, the description covers both the input constraint and the response structure, which is exactly the gap an absent output schema leaves. Nothing essential for correct invocation 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% (baseline 3), and the description adds a genuine constraint beyond the schema: the URL must contain an `article-<id>` path segment. That format requirement is not present in the schema text and helps the agent construct a valid input.

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 Mail article content) scoped to a single article by canonical URL. This clearly distinguishes it from the many sibling listing tools (dailymail_headlines, dailymail_news, dailymail_sections) which return collections rather than one article.

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?

The implied usage is retrieving one article when a canonical URL is known, and the `article-<id>` requirement hints at that. However, it never explicitly states when to use this vs dailymail_headlines or dailymail_sections, nor how to obtain the required URL, leaving routing to inference.

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