Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanityfair_article

Retrieve public Vanity Fair article metadata and body paragraphs from a canonical URL; subscriber-only pages return a permission error instead of partial or fabricated content.

Instructions

Get Vanity Fair article content. Returns public Vanity Fair article metadata and body paragraphs from a canonical article URL. A story Vanity Fair marks as subscriber-only in its own page metadata is reported as a permission error instead of a partial or fabricated body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Vanity Fair article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It does well by stating that only public content is returned and that subscriber-only articles produce a permission error rather than a partial or fabricated body. This is valuable edge-case transparency, though it does not mention rate limits, redirects, or invalid URL handling.

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 primary action and return type are front-loaded, and the paywall behavior is added as a focused second sentence. Every clause earns its place.

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?

For a single-parameter read tool with no output schema, the description is complete: it states the input (canonical URL), the output (metadata and body paragraphs), and the important permission-error case. Nothing else is needed for an agent to invoke it correctly.

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 coverage is 100%, and the schema already describes the url parameter as 'Canonical Vanity Fair article URL.' The description repeats the canonical-URL requirement without adding format details or examples, so it does not meaningfully exceed what the schema provides.

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 ('Get') and resource ('Vanity Fair article content'), and specifies what is returned: metadata and body paragraphs. It clearly distinguishes itself from sibling tools like vanityfair_headlines or vanityfair_sections by requiring a canonical article URL.

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: call this when you have a canonical Vanity Fair article URL and want its content. However, it does not explicitly contrast with sibling tools such as vanityfair_headlines, vanityfair_news, or vanityfair_author, nor state when NOT to use it.

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