Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanityfair_headlines

Get current Vanity Fair section headlines for a required section slug, returning each article’s title and URL.

Instructions

Get Vanity Fair section headlines. Lists the current headlines for one Vanity Fair section. section is required and takes hollywood, movies, television, award-season, what-is-cinema, culture, politics, business, style, beauty, fashion or royals. Each item has its title and URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesVanity Fair section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/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 full burden. It does disclose the return shape ('Each item has its title and URL'), which helps, but says nothing about pagination, freshness, rate limits, or ordering.

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 purpose in the first sentence, with the required parameter and return shape following. The long enumeration of section slugs duplicates the schema enum, which is mild but noticeable waste.

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-parameter read tool with no output schema, the description supplies the return shape (title and URL) and the full set of valid inputs, which is sufficient for correct invocation. Only deeper behavioral context is absent.

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 single enum parameter is fully documented in the schema. The description merely re-lists the enum values already present in the schema, adding no new semantics such as default behavior or formatting rules.

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 verb ('Get') and resource ('Vanity Fair section headlines') and scopes it to one section, which implicitly separates it from a broader vanityfair_news tool. It never names a sibling explicitly, so it falls short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no comparison to alternatives like vanityfair_news or vanityfair_sections, and no conditions or exclusions. It only states that 'section' is required, which is invocation mechanics rather than usage guidance.

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