Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vice_author

Fetch a VICE contributor profile from a required canonical URL; returns name, headshot, biography, and recent articles with title, summary, author, time, and image.

Instructions

Get a VICE contributor profile. Returns a VICE contributor profile from their canonical url (www.vice.com/en/contributor/<slug>, required). The response has the name and headshot when present, the biography paragraphs and recent articles with title, URL, summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical VICE contributor URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does useful work: it discloses the return shape in detail (name, headshot when present, bio paragraphs, recent articles with title/URL/summary/author/time/image). It omits any note on failure modes for an invalid slug, but for a read-by-URL tool this is solid disclosure.

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?

Purpose and required input are front-loaded, and the return-value sentence earns its place since no output schema exists. Minor redundancy in restating 'VICE contributor profile' twice across the first two sentences.

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, the description needs to convey what comes back and it does so thoroughly, plus the required input format. Missing only edge-case guidance (invalid or non-contributor URLs), which is minor for a single-parameter read tool.

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% but the schema's own description is terse ('Canonical VICE contributor URL'). The description adds real value by spelling out the expected URL pattern, www.vice.com/en/contributor/<slug>, which tells the agent what a valid input looks like.

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 (VICE contributor profile) with the exact input form. It is clearly distinguishable from vice_article, vice_news, and vice_headlines in practice, though it never names a sibling to contrast against.

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?

Implied usage only: it tells you the canonical contributor URL is required, which hints that you need a valid contributor page rather than a name or search term. No explicit when-to-use vs alternatives, no prerequisites, no exclusions.

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