Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timeslive_article

Extract article metadata and body paragraphs from a canonical TimesLIVE editorial URL, and detect when content is paywalled or access-restricted.

Instructions

Get TimesLIVE article content. Returns article metadata and body paragraphs for a canonical TimesLIVE editorial article URL. Some stories may have a publisher access gate; paywalled is set when the page's first-party access flags indicate restricted content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical TimesLIVE article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the return shape (metadata plus body paragraphs) and warns that some stories sit behind a publisher access gate, with a 'paywalled' indicator driven by first-party access flags. That gating behaviour is exactly the kind of trait an agent cannot get from the schema. It stops short of stating what happens on a gated page (partial content vs error), which keeps it below 5.

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 purpose, then the return contents, then the paywall caveat. Minimal waste, though the final sentence about 'first-party access flags' is slightly more mechanical detail than an agent needs to select the tool.

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 one-parameter read tool with no output schema, the description covers what is fetched, what comes back, and the main failure mode (paywalled content). Nothing critical is missing; only the behaviour on a gated request remains unspecified.

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 baseline is 3. The description reinforces that the URL must be canonical and belong to an editorial article, adding slight disambiguation beyond the schema's 'Canonical TimesLIVE article URL', but no format or edge-case detail.

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 TimesLIVE article content') and then specifies the return shape ('article metadata and body paragraphs'). It implies a boundary against siblings by insisting on a 'canonical TimesLIVE editorial article URL', which distinguishes it from timeslive_headlines/news/sections, but it never names those siblings, so routing still requires inference.

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?

There is no explicit when-to-use versus when-not-to-use guidance or naming of alternative tools. Usage is only implied by the phrase 'canonical TimesLIVE editorial article URL', which tells the agent it needs a full article URL rather than a section or author page, but nothing states which sibling to pick first when discovering content.

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