Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nymag_author

Fetch a New York Magazine author profile from a canonical author URL, returning name, job title, bio, and recent articles with titles, excerpts, sections, and published dates.

Instructions

Get a New York Magazine author profile. Returns a New York Magazine author profile from a required url in the form https://nymag.com/author/<slug>/. The response has name, job_title (empty for some contributors), bio and recent articles with title, URL, excerpt and a section label. Each article's published_at is the page's date text, such as Sept. 20, 2026, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical New York Magazine author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 it does disclose the return shape (name, job_title, bio, recent articles), the job_title-can-be-empty caveat, and the non-obvious published_at format quirk. It adds genuine behavioral context well beyond the schema, though it omits pagination/limits or failure behavior for the URL.

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?

Three tight sentences, front-loaded with the purpose, then input form, then return shape and the format caveat. No filler; the published_at note is a substantive quirk rather than padding.

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?

There is no output schema, so the description appropriately documents the response fields and their subtleties, and it fully specifies the single required input. Nothing an agent needs to call or interpret this tool 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?

Schema coverage is 100% (baseline 3), and the description adds real value beyond the schema's terse 'Canonical New York Magazine author URL' by specifying the exact URL form `https://nymag.com/author/<slug>/`, which pins down what a valid input looks like.

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 ('Get') and resource ('New York Magazine author profile') and distinguishes itself from the many sibling nymag_* article/headlines/news/sections tools by scoping to author profiles. An agent can tell instantly what it fetches.

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?

Usage is implied rather than stated: it says the tool needs a canonical author URL of a specific form, which implicitly tells the agent to use it when it has such a URL. There is no explicit when-to-use/when-not or named alternative (e.g. nymag_article for a single piece), so it stays at the implied-usage level.

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