Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yardbarker_headlines

Fetch recent Yardbarker headlines and summaries for a specific section using its slug. Returns title, URL, author, time, and image.

Instructions

Get headlines for a Yardbarker section. Lists recent Yardbarker headlines with short summaries for one section. section is required and takes a typed slug from yardbarker-sections, such as sport_1, team_18, school_506 or topic_16979. Items have title, URL, summary, author, time and image. Unknown slugs return a 400 error.

Input Schema

NameRequiredDescriptionDefault
sectionYesSection slug returned by /yardbarker/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/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 enumerates the returned fields (title, URL, summary, author, time, image) and discloses the 400 error on unknown slugs. It omits pagination/rate-limit behavior and read-only confirmation, which keeps it from a 5.

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?

Front-loaded with the core action and appropriately brief. The first two sentences partially restate each other ("Get headlines... Lists recent Yardbarker headlines"), a minor redundancy, but nothing is wasted overall.

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

Completeness5/5

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

For a single-param list tool with no output schema, the description covers purpose, param source with examples, returned item shape, and error behavior. Nothing essential for correct invocation is missing.

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 100% and the schema already explains the slug, but the description adds real value with concrete typed-slug examples (sport_1, team_18, school_506, topic_16979) and the 400-on-unknown-slug constraint, going beyond the schema text.

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?

States a specific verb ("Get headlines") and resource ("a Yardbarker section"), and clarifies it returns items for one section, which cleanly separates it from yardbarker_sections, yardbarker_author, and yardbarker_news. An agent can identify the tool's role without opening the schema.

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?

Points the agent at `yardbarker-sections` as the source of valid slugs, which is exactly the prerequisite an agent needs. It doesn't state when *not* to use it versus a sibling (e.g., yardbarker_news for general news), so it falls short of full when/when-not guidance.

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