Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dawn_headlines

Fetch Dawn section headlines by slug, returning title, URL, summary, publication time, and optional image for categories such as Pakistan, business, or sport.

Instructions

Get Dawn section headlines. Returns the latest Dawn headlines for one section. section is required and takes a slug such as pakistan, pakistan-sindh, world-south-asia, business-finance, sport-cricket, opinion or prism. Each item has its title, URL, summary, publication time and, when the outlet provides one, image.

Input Schema

NameRequiredDescriptionDefault
sectionYesDawn section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/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 usefully discloses the return fields (title, URL, summary, publication time, optional image), and 'Get' implies a safe read, but it says nothing about pagination, item counts, caching, or freshness beyond 'latest'.

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 before the parameter detail. The example-slug list is slightly redundant against the enum but remains scannable and not wasteful.

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 or annotations, the description covers the essential surface: what it fetches, the required slug format, and the shape of each returned item. Only pagination/volume behavior is left 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 coverage is 100% and the single 'section' parameter is a fully enumerated slug list with its own description, so the schema does the heavy lifting. The description's example slugs ('pakistan-sindh', 'sport-cricket', etc.) illustrate the format but add little beyond the enum.

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 (Get) plus resource (Dawn section headlines) and scopes it to 'one section', so an agent knows exactly what it returns. It does not explicitly differentiate itself from close siblings like dawn_news, dawn_sections or dawn_article, which would be needed for a 5.

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?

The description never says when to use this tool versus dawn_news, dawn_sections or dawn_article, nor that dawn_sections should be used to discover valid slugs. Usage is only implied by the required 'section' parameter.

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