Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailycaller_article

Retrieve The Daily Caller article metadata and body paragraphs from a canonical URL. Identifies paywalled premium articles by exposing only their public teaser.

Instructions

Get The Daily Caller article content. Returns public The Daily Caller article metadata and body paragraphs from a canonical article URL. Patriots-only (premium) articles expose only a public teaser and are flagged paywalled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical The Daily Caller article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that content is public, that premium 'Patriots-only' articles return only a teaser, and that such articles are flagged as paywalled. It does not mention authentication, rate limits, or failure cases, which are minor gaps for a read-only content fetcher.

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?

The description is two sentences with no wasted words. The core function is front-loaded, and the important paywall caveat is stated efficiently at the end.

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?

There is no output schema, so the description's mention of metadata, body paragraphs, and teaser/paywall behavior is helpful and largely sufficient. It does not enumerate specific metadata fields or error behaviors, but the tool is simple enough that an agent can invoke it correctly with this level of context.

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 schema covers the only parameter at 100% and already describes it as 'Canonical The Daily Caller article URL.' The description repeats the canonical-URL idea without adding materially new meaning, so the schema-description baseline of 3 applies.

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 clearly states the action and resource: 'Get The Daily Caller article content' and specifies the return values (metadata and body paragraphs). It is easy to distinguish from sibling tools like dailycaller_headlines or dailycaller_news, though it never explicitly names them.

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?

The description gives clear context: use this tool when you have a canonical article URL and want article metadata and body content. It does not mention alternatives or exclusion criteria for sibling tools, but the use case is clear enough for basic 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