Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailywire_sections

Lists Daily Wire content verticals like news, opinion, analysis, entertainment, upstream, and sports. Use the returned slugs with dailywire-headlines to fetch selected section headlines.

Instructions

Get Daily Wire content-vertical sections. Lists the Daily Wire content verticals that dailywire-headlines accepts, such as news, opinion, analysis, entertainment, upstream and sports. Each entry has a slug, name and url. Sampled on 2026-09-24, so the list may not be exhaustive.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses each entry's fields (slug, name, url) and warns the list was sampled on 2026-09-24 and 'may not be exhaustive' — a meaningful caveat about data currency and completeness. It does not discuss whether unknown slugs are rejected downstream, which keeps it at 4.

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 short sentences, front-loaded with the purpose and then the payoff (what the entries contain) and the caveat. Tight and readable, though the sample-date sentence could be phrased more compactly.

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 zero-parameter enumeration tool with no output schema, the description supplies everything needed: what it returns, the field names, concrete example values, and a freshness caveat. Only the degree of exhaustiveness/error behavior remains an open question.

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?

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description's mention of the returned `slug`, `name`, and `url` keys usefully describes output shape rather than inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get Daily Wire content-vertical sections') and immediately disambiguates against the sibling it feeds ('the Daily Wire content verticals that `dailywire-headlines` accepts'), so an agent knows this is the taxonomy endpoint rather than an article/headline endpoint.

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 link to `dailywire-headlines` makes the intended workflow clear: call this to discover valid section slugs before fetching headlines. There is no explicit "do not use when" clause or naming of a competing alternative, so it stops short of 5.

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