Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Luma Event Organizer Leads

find_luma_organizers

Find Luma event organizers by city and category and get one lead row per organizer with website, socials, follower count, events hosted, average guests, and paid-ticket share.

Instructions

Scrape Luma (lu.ma) events by city and category and get one lead row per organizer (website, socials, followers, events hosted, average guests, paid-ticket share), or raw event rows in 'events' mode. Priced per organizer or event. Runs the Apify actor zrk1212/luma-organizer-leads on your Apify account.

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": "find_luma_organizers"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOne row per organizer (default) or per event.
citiesNoLuma city slugs, e.g. ['sf', 'nyc', 'london'].
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
calendarsNoSpecific Luma calendar URLs or slugs (optional).
categoriesNoLuma categories, e.g. ['tech', 'ai', 'crypto'].
extraInputNoAny other input field of the Apify actor zrk1212/luma-organizer-leads, passed through as-is. See https://apify.com/zrk1212/luma-organizer-leads/input-schema
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
onlyPaidEventsNoOnly events with paid tickets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true, destructiveHint=false and non-idempotent behavior, so the safety bar is partly covered. The description adds genuinely useful context that annotations cannot: the run is priced per organizer or per event and executes on the caller's own Apify account, which is material for a costly, long-running scrape. It still doesn't state expected runtime or that the run may return partial results, which the schema covers only obliquely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the scrape scope and output shape, followed by cost and execution context. Every clause carries information an agent needs (what it returns, what it costs, where it runs); nothing is padding.

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 9 parameters, no required fields, a nested extraInput passthrough and no output schema, the description carries a real burden and mostly meets it by enumerating the returned lead fields and disclosing the cost model. It is only slightly short of complete because pagination/timeout behavior and the empty-result case are left entirely to the schema.

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. The description earns one step above that by explaining what 'events' mode actually produces ('raw event rows') and by tying the pricing model to the organizer-vs-event choice, giving the mode enum real meaning beyond its one-line schema text.

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 names a specific verb and resource ("Scrape Luma (lu.ma) events by city and category") and then states exactly what comes back: one lead row per organizer with named fields (website, socials, followers, events hosted, average guests, paid-ticket share), or raw event rows in 'events' mode. An agent can distinguish the two output modes without opening the schema, and the actor identifier nails down the data source.

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 mode split ('one lead row per organizer' vs 'raw event rows in events mode') implicitly guides which mode to pick, and the schema points to get_run_results for paging. However, the description gives no explicit when-to-use/when-not-to-use framing or prerequisites, so the agent must infer that this tool is for organizer lead generation rather than event-list browsing.

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