Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

engadget_headlines

Fetch Engadget headlines for a specified section slug to retrieve category-specific news articles in structured JSON.

Instructions

Get Engadget section headlines. Returns the latest Engadget headlines for one category. section is required and takes one of 48 slugs such as ai, gaming, apple, laptop-pc-reviews or transportation-evs; other values return an invalid-parameter error. Small categories, such as buying guides, may hold only a few items.

Input Schema

NameRequiredDescriptionDefault
sectionYesEngadget category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds useful behavioral context: invalid section values return an invalid-parameter error, and small categories may return only a few items. Still missing any note on result count, pagination, freshness, or auth — meaningful gaps for a headlines feed.

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 sentences, front-loaded with purpose followed by the required parameter and an edge-case note. Every sentence contributes; no padding.

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 tool with full enum coverage and no output schema, the description covers purpose, the required parameter, valid inputs, and the small-category caveat. It is essentially complete, with only result-shape details left unstated (which is acceptable without an output schema).

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 coverage is 100% with a full 48-value enum, so the baseline is 3. The description adds marginal value by noting the slug count, giving examples, and stating that other values error, but it largely restates what the enum already enumerates.

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?

States a specific verb and resource: 'Get Engadget section headlines' and 'Returns the latest Engadget headlines for one category.' This clearly distinguishes the filtered-per-category nature of the tool, though it does not explicitly contrast with siblings like engadget_sections or engadget_news.

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 description makes clear it fetches headlines for exactly one category and that `section` is required, implying usage. However it offers no guidance on when to reach for this over engadget_news, engadget_sections, or engadget_article, and gives no exclusions.

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