Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

billboard_article

Extract Billboard article metadata and body paragraphs from a canonical URL, flagging Pro teaser pages as paywalled.

Instructions

Get Billboard article content. Returns public Billboard article metadata and body paragraphs from a canonical article URL. Billboard Pro articles are returned in full when the public page serves the full body; a teaser-only page is flagged paywalled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Billboard article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 disclosure burden. It adds genuinely useful behavioral context: only public articles are returned, Pro articles may be full or teaser-only, and teaser-only pages are flagged as paywalled. This goes beyond a bare 'get article' statement.

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 concise sentences with no filler. The primary behavior is front-loaded, and the paywall nuance is placed second where it adds value without obscuring the main purpose.

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 endpoint with no output schema, the description adequately covers the input, the returned content type, and the paywall/teaser behavior. It could list exact fields or error behavior, but nothing critical for basic invocation is missing.

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 already documents the only parameter, url, as 'Canonical Billboard article URL' with 100% coverage. The description repeats 'canonical article URL' but adds no format details, examples, or edge-case guidance beyond the schema.

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 opens with a specific verb and resource ('Get Billboard article content') and specifies the output (metadata and body paragraphs) and input (canonical article URL). It is clear, though it does not explicitly contrast itself with sibling tools like billboard_author or billboard_headlines.

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?

The usage context is implied: use this when you have a canonical Billboard article URL and want article content. However, it never names alternatives or states when not to use this tool, so the agent must infer the distinction from sibling names.

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