Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dawn_article

Fetch structured Dawn.com article content by canonical URL, returning title, authors, publish/update times, section, lead image, and body paragraphs as JSON.

Instructions

Get Dawn article content. Returns one Dawn article by its canonical url in the form https://www.dawn.com/news/<id>/<slug>. The response has the title, description, publish and update times, section, authors, lead image and body paragraphs. Blocked or malformed pages return an upstream error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Dawn article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 burden and does reasonably well: it enumerates the returned payload (title, description, publish/update times, section, authors, lead image, paragraphs) and discloses the failure mode for blocked or malformed pages. It omits permission/auth requirements and rate-limit behavior, but for a read-only fetch these are lower-stakes gaps.

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 short sentences, front-loaded with the action and resource, then input format, then return shape and error case. No filler or repetition.

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 fetch tool with no output schema and no annotations, the description covers input format, returned fields, and error behavior. Nothing essential is missing, though it could note whether the tool expects the full URL versus an ID.

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 100%, so the single param is already documented. The description still adds real value by giving the exact accepted URL shape (https://www.dawn.com/news/<id>/<slug>), which tells the agent what a valid input looks like beyond the schema's generic 'Canonical Dawn article URL'.

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 Dawn article content', 'Returns one Dawn article'), which is unambiguous. It does not explicitly contrast itself with the Dawn siblings (dawn_headlines, dawn_news), though the singular 'one article by its canonical url' framing makes the distinction inferable.

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

Usage Guidelines2/5

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

No statement of when to use this versus dawn_news, dawn_headlines, or dawn_sections, and no prerequisites beyond the implicit URL requirement. The only conditional language ('Blocked or malformed pages return an upstream error') describes failure behavior, not usage selection.

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