Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

dailywire_headlines

Fetch current Daily Wire headlines for a chosen content section. Provide a section slug to retrieve its front-page headlines; an empty result means that vertical is not featured.

Instructions

Get Daily Wire section headlines. Returns current Daily Wire headlines for one content vertical. section is required and takes news, opinion, dw-opinion, analysis, news-and-commentary, news-and-analysis, exclusive, entertainment, original, upstream, sports or mi-x-dw. An empty result means the front page does not currently feature that vertical.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Wire section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a useful behavioral edge case ('an empty result means the front page does not currently feature that vertical'), but says nothing about freshness, result limits, or whether section slugs are stable, leaving most behavioral traits unstated for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and empty-result note are front-loaded and useful, but re-listing all twelve enum values already present in the schema consumes most of the text without adding value. Trimming that list would sharpen the definition considerably.

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 required-enum, read-only headline endpoint with no output schema, this covers the essentials: what it returns, the required parameter, and the empty-result behavior. Only minor gaps remain around freshness and how it relates to sibling endpoints.

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 enum is already fully documented in the schema, so the description's enumeration of all twelve slugs is largely redundant. It adds only marginal meaning by framing `section` as a 'content vertical', so the baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Get Daily Wire section headlines') and clarifies it returns headlines for one content vertical. This distinguishes it reasonably from dailywire_article and dailywire_author, but it never explicitly differentiates from the close siblings dailywire_news and dailywire_sections, which an agent might confuse it with.

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 ('for one content vertical') and the empty-result caveat hints at how front-page curation works, but there is no explicit guidance on when to pick this over dailywire_news or dailywire_sections, nor any stated prerequisites.

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