Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

variety_article

Get structured Variety article data by URL: title, authors, section, images, body, and paywall status. Use for content analysis or aggregation.

Instructions

Get Variety article content. Returns one Variety article by its canonical variety.com url, in the form /<year>/<vertical>/<subcategory>/<slug>-<id>/. The response has the title, description, authors, section, published and updated times, lead image, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Variety 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 provided, the description carries the burden and does reasonably well: it enumerates the returned fields and discloses a `paywalled` flag, which is a meaningful behavioral trait an agent needs. It omits any mention of authentication, permissions, or rate limits, so it stops short of full transparency.

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, then the URL format, then the response shape. No filler, though the final field list is dense and could be slightly compressed.

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 compensates by describing the return fields and the paywalled flag, and by specifying the accepted URL format. For a single-parameter fetch tool this is close to complete, lacking only auth/error-handling context.

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% (the url param is already documented), so the baseline is 3. The description earns above that by giving the canonical path template `/<year>/<vertical>/<subcategory>/<slug>-<id>/`, which adds real construction/validation value beyond the schema's brief 'Canonical Variety article URL'.

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 states a specific verb and resource ('Get Variety article content') and clarifies scope as 'one Variety article by its canonical url'. This cleanly distinguishes it from siblings like variety_headlines, variety_news, variety_sections, and variety_author, which return lists or author data rather than a single article body.

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?

It implies usage by requiring a canonical URL, which signals this is the fetch-a-known-article tool rather than a discovery tool. However, it never names the alternatives (e.g., variety_news or variety_headlines) or states when-not to use it, so the routing guidance is only implied.

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