Crawlora MCP

vanityfair_headlines

Read-only

Current Vanity Fair headlines for one public section; section must come from vanityfair_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "vanityfair_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Vanity Fair section slug. Documented values: hollywood, movies, television, award-season, what-is-cinema, culture, politics, business, style, beauty, fashion, royals.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / section / description

Added value: +"Vanity Fair section slug. Documented values: hollywood, movies, television, award-season, what-is-cinema, culture, politics, business, style, beauty, fashion, royals."

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the 'public section' scoping constraint and the section-source requirement, but says nothing about freshness, pagination or result volume beyond 'current'.

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?

A single front-loaded sentence that states the resource and its scoping constraint with zero filler.

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?

With an output schema present, the description needn't explain return values, and it adequately covers the one required parameter's source. It is nearly complete for a simple single-parameter list tool, missing only explicit sibling disambiguation.

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 schema already lists all documented section slugs, so the schema carries the parameter semantics. The description's only added value is the requirement that the slug originate from vanityfair_sections, which is a useful but marginal addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Vanity Fair headlines) with a scope qualifier ('current', 'one public section'), which is enough for an agent to understand the tool. It does not explicitly differentiate itself from sibling vanityfair_news, so an agent must infer the headlines-vs-news distinction.

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?

It gives a concrete dependency: the section value 'must come from vanityfair_sections', which routes the agent correctly when it needs valid input. It stops short of naming when to choose this over vanityfair_news or vanityfair_article.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?