Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailycaller_headlines

Fetch up to 40 recent Daily Caller headlines for a required section slug, returning titles, URLs, and lead images as clean JSON.

Instructions

Get The Daily Caller section headlines. Returns the newest headlines, about 40, from one Daily Caller section page. section is required (politics, world, energy, opinion, patriots and others); any other value returns a 400. Items have a title, URL, lead image and sometimes a type such as opinion. Section pages carry no publish time or byline.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Daily Caller section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the approximate result count (~40), the fields per item (title, URL, lead image, optional type), the error behavior for invalid sections, and the important data limitation that section pages carry no publish time or byline.

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?

Purpose is front-loaded, followed by result shape, parameter constraint, item contents and a caveat. Four tight sentences with no filler; even the example values aid the agent.

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, the description covers the return contents and their limitations adequately. Missing only auth/rate-limit context, which is minor for a public headline feed.

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 already 100% with an enum, so the baseline is 3. The description adds genuine meaning beyond the schema by noting the parameter is required and that any value outside the accepted set returns a 400, clarifying the failure mode.

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 The Daily Caller section headlines') and immediately scopes it to 'one Daily Caller section page'. It is clear what the tool returns, though it never explicitly distinguishes itself from siblings like dailycaller_news or dailycaller_sections.

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?

It gives a required-parameter constraint and the consequence of a bad value (400), which is useful. However, it never says when to choose this tool over dailycaller_news or dailycaller_article, leaving usage context implied rather than stated.

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