Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vanityfair_author

Fetch a Vanity Fair contributor profile from its canonical URL to get name, title, biography, headshot, social links, and recent articles.

Instructions

Get a Vanity Fair contributor profile. Returns a Vanity Fair contributor profile from their canonical url (www.vanityfair.com/contributor/<slug>, required). The response has the name, job title when present, biography, headshot, social links and recent articles with title, URL and publication time.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Vanity Fair contributor URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 full behavioral burden. It helpfully enumerates the response fields (name, job title, biography, headshot, social links, recent articles), which is real disclosure. However, it omits auth/permission needs, error behavior, and historical vs current data handling.

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?

Two sentences, purpose front-loaded, no filler. The second sentence is dense but each clause (fields, article sub-fields) earns its place for a tool with no output 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?

With no output schema and no annotations, the description adequately covers the input format and the return shape. It is complete enough to invoke correctly, missing only edge-case/error behavior which is minor for a single-parameter read.

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 goes beyond the schema's terse 'Canonical Vanity Fair contributor URL' by stating the exact URL pattern (`www.vanityfair.com/contributor/<slug>`) and marking it required. This adds genuinely useful format guidance.

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+resource ('Get a Vanity Fair contributor profile') and the scope is unambiguous against siblings like vanityfair_article and vanityfair_news. An agent can immediately tell this returns contributor metadata rather than articles.

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 use case is implicitly clear from 'Get a Vanity Fair contributor profile', but there is no explicit when-to-use guidance, no mention of alternatives (e.g., vanityfair_article for content), and no prerequisites stated. Usage is implied rather than delineated.

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