Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vice_article

Fetch a VICE article by canonical URL to get its title, authors, section, timestamps, lead image, body paragraphs, and paywalled status in structured JSON.

Instructions

Get VICE article content. Returns one VICE article by its canonical url, in the form www.vice.com/en/article/<slug>. The response has the title, description, authors, section, published and updated times, lead image and body paragraphs, plus a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical VICE article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does so well: it enumerates the returned fields (title, description, authors, section, published/updated times, lead image, body paragraphs) and flags a `paywalled` trait that tells the agent content may be gated or truncated. It omits auth needs and rate limits, so it is not a 5.

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 sentences, front-loaded with purpose, then input format, then return shape — every sentence carries information and none is redundant. The return-field sentence is long but justified since no output schema exists.

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 simple one-parameter read tool with no output schema and no annotations, the description is complete enough to call correctly: it specifies the input format and the return payload, including the paywalled caveat. Only peripheral operational details (auth, limits) are absent.

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%, so the baseline is 3, but the description adds real meaning beyond the schema's terse 'Canonical VICE article URL' by giving the exact format `www.vice.com/en/article/<slug>`. That format detail is genuinely useful for constructing a valid input.

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 and resource: 'Get VICE article content... Returns one VICE article by its canonical url.' This clearly separates it from sibling feed/navigation tools like vice_news, vice_sections, and vice_author by emphasizing a single article fetched by URL. It stops short of naming any sibling explicitly, so it earns a 4 rather than a 5.

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?

The description implies the use case (you must already have a canonical article URL) but never states when to choose this over siblings like vice_news or vice_author, nor any prerequisites or exclusions. With no explicit when/when-not guidance, this falls to a 2.

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