Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailywire_author

Retrieve a Daily Wire author's public profile, including name, headshot, biography, social handles, and recent articles, by providing their slug or profile URL.

Instructions

Get a Daily Wire author profile. Returns one Daily Wire staff writer or contributor's public profile: name, headshot, social handles when present, biography, and their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical dailywire.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. brent-scher

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?

No annotations are provided, so the description carries the full burden. It clearly indicates a read operation returning a public profile and honestly notes social handles are included 'when present.' It does not cover error cases, rate limits, or auth, but this is a simple public fetch with no side effects.

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?

Two concise sentences with no wasted words. The purpose is front-loaded, and the returned fields are listed efficiently. Minor repetition of 'Daily Wire' and 'profile' is harmless and does not affect clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations are present, so the description must compensate. It lists the main fields returned but omits critical input guidance: both url and slug are optional in the schema, and the description does not state that one is required or how to choose. The phrase 'recent articles' is also vague. This is a meaningful gap for correct invocation.

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 description coverage is 100%, so baseline is 3. The description adds no parameter-level meaning beyond the schema; it does not clarify whether url or slug is preferred or whether one is mandatory for a successful call. The schema already documents the parameters well.

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: getting a Daily Wire author profile, and lists returned fields (name, headshot, socials when present, biography, recent articles). It does not explicitly differentiate from sibling tools, but the name and content make distinction clear.

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: an agent would use this when it needs a Daily Wire author profile. However, there is no explicit guidance on when to use it versus sibling tools (e.g., dailywire_article or other outlet author tools), and no when-not or alternative routing. It is adequate but not instructive.

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