Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dw_article

Fetch Deutsche Welle article or live-blog content by canonical URL, returning title, description, publish time, section, authors, lead image, and body paragraphs.

Instructions

Get DW article content. Returns one Deutsche Welle article by its canonical url, either a standard /en/<slug>/a-<id> article or a /en/<slug>/live-<id> live-blog page. The response has the title, description, publish time, section, authors, lead image and body paragraphs. Blocked or malformed pages return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical DW article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 reasonable work: it discloses that exactly one article is returned, the accepted URL formats, the response contents, and that blocked or malformed pages produce an upstream error. It stops short of stating auth/permission needs or any rate limits, which would be the remaining gap for a fetch tool.

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?

Three sentences, none wasted: purpose and input first, then accepted formats, then return payload and failure mode. Front-loaded and easy to scan.

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?

No output schema exists, so the description compensates by listing the returned fields (title, description, publish time, section, authors, lead image, paragraphs) and covering the error case, which is most of what an agent needs. Minor omissions like language/locale coverage are acceptable.

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%, but the description adds real value by enumerating the valid URL shapes (`/en/<slug>/a-<id>` and `/en/<slug>/live-<id>`), which prevents an agent from passing a section or homepage URL to a single-article endpoint.

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 DW article content'), scopes it to a single article, and names the two URL shapes it accepts. It does not explicitly contrast itself with list-oriented siblings like dw_headlines or dw_news, so an agent must infer that those supply the URLs this tool consumes.

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: it takes 'its canonical url,' which quietly signals that a URL must come from another endpoint (headlines/news/sections). There is no explicit when-to-use/when-not guidance or named alternative.

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