Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

gizmodo_headlines

Retrieve Gizmodo headlines for a required section slug, returning each item’s title, URL, summary, author, publication time, and image.

Instructions

Get Gizmodo section headlines. Returns the latest Gizmodo headlines for one section. section is required and takes a slug such as gadgets, artificial-intelligence, io9, science or deals; any other value returns an invalid-params error. Each item has its title, URL, summary, publication time, author and image. Use gizmodo-sections to list the slugs.

Input Schema

NameRequiredDescriptionDefault
sectionYesGizmodo section slug

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 full burden and does meaningful work: it discloses the invalid-params error on bad input and enumerates the returned item fields (title, URL, summary, publication time, author, image). It omits auth, rate-limit, and pagination behavior, but for a simple read tool this is solid disclosure.

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 and efficient, with purpose first, then return shape, error behavior, and the sibling pointer. The opening two sentences overlap slightly ('Get Gizmodo section headlines' vs 'Returns the latest Gizmodo headlines for one section'), a minor redundancy.

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?

No output schema and no annotations, so the description must supply everything. It covers purpose, required param semantics, error behavior, and return fields, leaving only minor gaps like pagination or result count for a single-parameter read tool.

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 enum already lists every valid slug, so the examples are partly redundant. However, the description adds the behavioral fact that any value outside the accepted slugs returns an invalid-params error, which is not expressible in the schema.

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+resource+scope: 'Get Gizmodo section headlines' and 'Returns the latest Gizmodo headlines for one section'. An agent knows exactly what it retrieves and that it is scoped to a single section, which separates it from a general feed. It also names the related gizmodo-sections tool.

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?

Gives clear context ('one section') and routes the agent to gizmodo-sections to discover valid slugs, plus warns that other values error. It does not explicitly contrast with the sibling gizmodo_news, so the when-to-use-this-vs-alternative guidance is present but incomplete.

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