Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gq_sections

Retrieve the 11 GQ sections used by gq-headlines, with slug, display name, and URL, skipping pages that list no stories.

Instructions

Get GQ sections. Lists the 11 GQ sections accepted by gq-headlines: culture, entertainment, fitness, gq-hype, gq-recommends, gqsports, grooming, politics, style, watches and wellness. Each entry has a slug, display name and section url. Pages that list no stories are not included.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and does so partially: it discloses the return shape (slug, display name, url) and the filtering rule that empty sections are omitted. It does not mention caching, ordering, or whether the list is static, but no safety/annotation concerns arise for a read-only catalog call.

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 verb plus resource, then the useful slug list, then the return shape. The 11-slug enumeration is verbose but is the tool's actual payload, so it earns its space; a line break or two would improve scanability marginally.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description must convey the return fields and the exclusion rule, and it does both explicitly. Nothing an agent needs to call this correctly is missing.

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?

Zero parameters, so the baseline is 4. The enumerated slugs are effectively the tool's value domain rather than parameters, and the description supplies them directly.

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 and resource ('Get GQ sections') and immediately scopes it by naming the sibling it supports (`gq-headlines`). An agent can distinguish it from gq_headlines, gq_news and gq_article without opening a schema.

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?

The tie to `gq-headlines` implies the intended usage as a lookup/validator for section slugs, which is real context. It stops short of explicit when-to-use / when-not-to-use guidance or naming an alternative enumeration tool.

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