Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gq_author

Retrieve a GQ contributor's public profile, including biography, headshot, social links, and recent articles, by providing their contributor slug or profile URL.

Instructions

Get a GQ contributor profile. Returns one GQ contributor's public profile: name, biography, headshot, social links, and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical www.gq.com/contributor/<slug> URL; alternative to slug
pageNo1-based page of the contributor's article list (1-100)
slugNoContributor slug, e.g. tom-ward; provide slug or url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

There are no annotations, so the description carries the behavioral burden; it does this well by listing the returned fields and noting that only 'one page' of recent articles is returned. It does not cover not-found behavior or authentication, but as a public read-only profile fetch, the disclosed return shape is the core behavioral contract.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler: the first states the action and resource, the second lists the return contents. Every sentence earns its place and the key scope constraint ('one page') is included.

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 simple profile fetch with no output schema and no annotations, the description compensates by enumerating the return fields and page scope. The schema fully covers the slug/url/page parameters; the only minor gap is no explicit statement that one of slug or url should be supplied, but the schema already says 'provide slug or url'.

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%, so the baseline is 3; the description adds no parameter-specific meaning beyond the schema. The phrase 'one page' loosely relates to the page parameter, but slug/url/page semantics are already fully documented 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?

The description uses a specific verb and resource: 'Get a GQ contributor profile' and then enumerates what is returned. It is clearly distinct from sibling article, headline, news, and section tools by naming GQ and the contributor-profile scope.

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 intended use is implied clearly: use this when you need a GQ contributor's public profile and their recent articles. However, it does not explicitly state when not to use it or name alternatives such as gq_article for full article content, leaving the selection guidance implicit.

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