Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomsguide_headlines

Fetch current headlines for a chosen Tom's Guide section by slug, returning each item's title, URL, summary, author, publication time, and image.

Instructions

Get Tom's Guide section headlines. Returns the current headlines for one Tom's Guide section. section is required and takes one of 22 slugs, such as ai, audio, deals, how-to, news, reviews, tvs or phones. Each item has its title, URL, summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesTom's Guide section 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?

No annotations are provided, so the description carries the burden. It clarifies that the operation is scoped to a single section and enumerates the returned fields (title, URL, summary, author, publication time, image), which is useful. It says nothing about read-only semantics, caching, rate limits, or ordering of headlines, so behavioral coverage is partial.

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 tight sentences, front-loaded with the action and scope, then constraint, then return shape. Little waste; the example-slug list is slightly redundant with the enum but still reads efficiently.

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?

With no output schema, the description steps in by listing the fields each item contains, and it explains the required section parameter. Together with the schema, an agent has enough to call it correctly; only the sibling-routing information 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?

Schema description coverage is 100% and the enum lists all 22 slugs, so the structured data already documents the parameter fully. The description adds informal example slugs ('ai', 'audio', 'deals') and the count of 22, which is only marginal value over the schema. Baseline 3 applies.

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 Tom's Guide section headlines.' A reader immediately knows it returns current headlines for a single section, and the field list confirms the shape of each item. It does not explicitly distinguish itself from close siblings like tomsguide_news or tomsguide_sections, so it falls short of a 5.

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 implies usage ('for one Tom's Guide section') but never states when to choose this over tomsguide_news, tomsguide_sections, or tomsguide_article. With four closely-named siblings the absence of routing guidance is a real gap, leaving the agent to infer the boundary.

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