Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivegoogle_headlines

Retrieve recent 9to5Google headlines for a specified section slug, such as gemini or wear-os, to track Google and Android news by topic.

Instructions

Get 9to5Google section headlines. Returns recent 9to5Google headlines for one guide or editorial archive. section is required and takes a slug such as gemini, google-pixel-9 or wear-os; an unknown or missing value returns an invalid-params error. There are 58 guide feeds and five editorial archives, and some hold fewer than 100 entries.

Input Schema

NameRequiredDescriptionDefault
sectionYesSlug returned by ninetofivegoogle_sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 behavioral burden. It usefully discloses error behavior for invalid sections and notes the number and size range of available feeds, but it omits read-only confirmation, authentication needs, rate limits, and return-list behavior such as pagination or ordering.

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?

The description is front-loaded and appropriately sized: purpose first, parameter behavior second, and feed inventory context last. The final sentence about feed counts and entry limits is mildly extraneous but still useful for expectation setting.

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 one-parameter, read-style feed tool with no output schema and no annotations, the description covers identity, required input, error behavior, and source scope. It could say more about the returned headline shape or ordering, but it is largely complete for correct invocation.

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 description coverage is 100%, so the enum and slug description already define the parameter. The description still adds value by explaining that the slug represents a guide or editorial archive, giving concrete examples, and clarifying what happens for unknown or missing values.

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 states a specific verb and resource: 'Get 9to5Google section headlines' and 'Returns recent 9to5Google headlines for one guide or editorial archive.' It clearly scopes the tool to section feeds rather than general news or articles, but it does not explicitly name or differentiate from siblings such as ninetofivegoogle_news or ninetofivegoogle_sections.

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?

It establishes that `section` is required, gives example slugs, and warns that unknown/missing values produce an invalid-params error. However, it does not explicitly say when to use this tool versus related alternatives like ninetofivegoogle_news or ninetofivegoogle_sections, leaving selection guidance to inference.

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