Skip to main content
Glama

Van Born Labs tool catalog

vanborn_labs_catalog
Read-onlyIdempotent

List available MCP tools and Apify Store actors, including configured but disabled ones, to discover scrapers and monitors before starting any Apify run or incurring charges.

Instructions

List Van Born Labs MCP tools and Apify Store actors, including ones that are configured but not yet enabled. Use this to discover YouTube scrapers, Google News, email validators, job scrapers, GTA 6 monitors, hiring signals, ads radar and reviews monitor. No Apify run is started and nothing is billed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vanborn_labs_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description still adds value beyond them by asserting 'No Apify run is started and nothing is billed' (a cost/activation guarantee an agent cannot infer from readOnlyHint alone) and by disclosing that the listing includes configured-but-not-enabled entries, which affects how the agent should interpret results.

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, front-loaded with the core action and followed by routing hints and the cost caveat; nothing is buried. The mid-sentence category list is long, but each domain keyword earns its place as a discovery hook for matching a user's request to this catalog.

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 parameters, no output schema and full annotation coverage, the remaining burden is describing what comes back and at what cost — both of which the description handles ('tools and actors', 'configured but not yet enabled', 'nothing is billed'). It stops short of describing the returned record shape (names, enablement flags), which is the only meaningful gap for a discovery 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?

The tool takes no parameters, so there are no parameter semantics to document; the baseline for zero-param tools applies. The description sensibly spends its space on what the call returns and its cost profile instead of inventing input detail.

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 opens with a specific verb and resource — 'List Van Born Labs MCP tools and Apify Store actors' — and adds the non-obvious scope 'including ones that are configured but not yet enabled.' It then enumerates concrete content domains (YouTube scrapers, Google News, email validators, GTA 6 monitors), which clearly separates this catalog/discovery tool from the operating siblings like youtube_comments or google_news_rss.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to discover ...' gives an explicit trigger condition: reach for this tool when you need to find which scraper or validator exists before invoking one. It does not state a when-not condition or name a competing discovery route, but with zero required parameters there is little ambiguity about when to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.