Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gq_headlines

Retrieve GQ section headlines and story cards by section slug, returning title, URL, summary, author, image, and date for /story/ articles.

Instructions

Get GQ section headlines. Returns the story cards currently on one GQ section page. section is required and takes one of 11 slugs such as style, grooming, watches or gqsports. Each item has its title, url, summary, author, image_url and a published_at date (YYYY-MM-DD). Only /story/ articles are listed, and fields GQ does not show are omitted.

Input Schema

NameRequiredDescriptionDefault
sectionYesGQ section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 well: it discloses the returned entity (story cards), the item fields, the published_at format, and two behavioral constraints ('only /story/ articles are listed', 'fields GQ does not show are omitted'). It stops short of noting rate limits or that this is a read/scrape operation.

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-loads purpose in the first sentence, then layers return shape and constraints. Mostly earns its sentences, though the slug enumeration partially duplicates the schema's enum.

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 or annotations exist, so the description must stand in for both; it describes item fields, the date format, and filtering constraints. Complete enough for a single-param read tool, missing only auth/rate-limit framing.

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 11-value enum already documenting valid slugs, so the schema does the heavy lifting. The description reiterates that `section` is required and is one of 11 slugs with four examples, adding only marginal value over the structured field.

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 ('Get GQ section headlines') and scopes it to 'one GQ section page,' which cleanly separates it from siblings like gq_sections (which lists sections), gq_news, and gq_author. An agent can tell what it returns without opening the schema.

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 'one GQ section page' scoping implies you fetch a single section's cards, and the required `section` param hints at the workflow. However, it names no alternative (e.g. gq_sections for the slug list, or gq_news for general headlines) and gives no explicit when/when-not guidance.

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