Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dw_headlines

Fetch Deutsche Welle headlines for a chosen section by slug, returning each article's title, URL, and image when available.

Instructions

Get DW section headlines. Returns the latest Deutsche Welle headlines for one section. section is required and takes one of 18 slugs, such as africa, middle-east, germany, climate, migration, human-rights, business or sports. Each item has its title and URL, plus an image when the card shows one.

Input Schema

NameRequiredDescriptionDefault
sectionYesDW section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 does disclose the return shape ('Each item has its title and URL, plus an image when the card shows one'), which is genuinely useful given there is no output schema, but it says nothing about item counts, freshness, pagination, or rate limits.

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 the purpose and then the return shape. Every sentence contributes, though the slug examples partially duplicate the schema enum rather than adding new information.

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 single-parameter read tool with no output schema and no annotations, the description covers the resource, the required argument, the valid slug family, and the fields returned. It is only missing second-order details such as how many headlines come back and how fresh they are.

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% and the enum already enumerates all 18 slugs. The description repeats that `section` is required and lists eight example slugs, which mostly duplicates structured data; baseline 3 applies.

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 section headlines ... latest Deutsche Welle headlines for one section') and scopes it to a single section, which separates it from the broader dw_news. It never explicitly names or rules out sibling tools like dw_sections or dw_article, so it stops short of full sibling differentiation.

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 resource ('one section'), but there is no explicit when-to-use guidance, no when-not condition, and no named alternative for an agent that wants general news versus section-scoped headlines. Adequate but with clear gaps.

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