Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyexpress_article

Retrieve one Daily Express article by canonical URL for structured title, description, publish/update times, section, authors, lead image, body paragraphs, and paywalled status.

Instructions

Get Daily Express article content. Returns one Daily Express article by its canonical article url. The response has the title, description, publish and update times, section, authors, lead image, body paragraphs and a paywalled flag. Subscriber-only or blocked articles return an upstream error instead of partial text.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Daily Express article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does useful work: it enumerates the returned fields (title, description, publish/update times, section, authors, lead image, body paragraphs, paywalled flag) and discloses that subscriber-only or blocked articles fail with an upstream error rather than partial text. It omits auth, rate-limit, or caching behavior, but the error-failure disclosure is genuinely valuable beyond the schema.

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 tight sentences, front-loaded with the purpose, then return shape, then the error caveat. Slight redundancy between 'Get Daily Express article content' and 'Returns one Daily Express article,' but nothing that wastes meaningful space.

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, no-output-schema tool with no annotations, the description is sufficient: it covers what is fetched, what the response contains, and the key failure mode. An agent has everything needed to invoke it correctly.

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 coverage is 100% and there is only one parameter, so the schema already documents `url`. The description reinforces that it must be the canonical article URL, matching the schema wording, but adds no format or syntax detail beyond it. Baseline 3 is appropriate.

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 (Get) and resource (Daily Express article content) with clear scope: one article identified by canonical URL. It does not explicitly name a sibling (e.g., dailyexpress_headlines) to route the agent, but the singular-article framing distinguishes it well enough from the sections/news/author siblings.

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 by the URL-based single-article scope, but there is no explicit when-to-use/when-not guidance or pointer to sibling tools for listing headlines or browsing sections. Adequate but leaves the agent to infer when this is the right call.

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