Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nymag_headlines

Fetch recent New York Magazine headlines for a chosen section slug, returning story titles, URLs, and optional story details.

Instructions

Get New York Magazine section headlines. Returns recent New York Magazine stories for one site section. section is required and takes one of nine slugs: intelligencer, thecut, vulture, grub-street, curbed, strategist, select-all, science or daily. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNew York Magazine section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 behavioral burden. It discloses the return shape (title, URL, optional summary/author/publication time/image), which is useful since there is no output schema, but it omits pagination, result limits, and refresh/recency behavior for a feed-style endpoint.

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 purpose and then the required parameter and return shape. Every sentence contributes; only the verbatim slug enumeration is mildly redundant with the schema.

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 single-required-parameter tool with no output schema and no annotations, the description covers purpose, the required argument, and the item shape well. The only gap is pagination/volume behavior, which is minor but unaddressed.

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 is fully defined in the schema. The description restates the nine slugs verbatim and adds no syntax or meaning beyond what the schema already provides, so the baseline of 3 applies.

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 New York Magazine section headlines') and scopes it to 'one site section'. An agent can distinguish this from siblings like nymag_sections, nymag_news and nymag_article without opening any 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 description notes the tool returns stories for a single section and that `section` is required, which implies the usage context. However, it never states when to prefer this over sibling tools such as nymag_news or nymag_sections, and gives no exclusions or prerequisites.

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