Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dw_author

Fetch a Deutsche Welle correspondent's public profile and recent articles using their canonical person URL. Returns name, expertise, biography, and article links.

Instructions

Get a DW author profile. Returns one Deutsche Welle correspondent's public profile (name, expertise, biography) and their recent articles from a canonical person-profile URL. Many DW breaking-news items are bylined to the "Deutsche Welle" editorial organization rather than a named person; those articles have no person-profile URL to look up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical www.dw.com/en/<name>/person-<id> URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states it returns profile fields and recent articles, and notes a limitation (editorial bylines have no profile URL). It does imply a read-only lookup without explicitly saying so, but the behavior is clear enough for an agent.

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 with zero redundancy. The main purpose is front-loaded, followed by a useful caveat. Every sentence earns its place.

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, it explains what is returned, how the URL behaves (canonical), and flags an important edge case. Minor omissions like error behavior or pagination do not detract much given the simplicity.

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?

The input schema already describes the url parameter as a canonical www.dw.com/en/<name>/person-<id> URL, covering 100%. The description adds no additional parameter-level detail, so per the baseline rule for high coverage, a 3 is appropriate.

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 and resource: 'Get a DW author profile.' It clearly distinguishes from sibling author tools by the DW domain and enumerates returned contents (name, expertise, biography, recent articles). No ambiguity about which outlet or endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an implicit when-not-to-use guideline: articles bylined to the 'Deutsche Welle' editorial organization have no person-profile URL, so this tool is not applicable. This helps avoid misuse. However, it does not explicitly name alternative tools or conditions for using them, so it stops short of a 5.

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