Open Call Portal

Returns the Open Call Portals discovery contract: portal IDs, field value options, MCP server details, and read-only search metadata. Call this first for autodiscovery before filtering searches.

無需輸入參數。

Use this when talent, crew, suppliers, or service providers are looking for posted work: gigs, jobs, opportunities, vacancies, slots, bookings, wanted/needed listings, or open calls. Treat those words as search intent—not as genre/type filters. For example, 'DJ gig Amsterdam', 'DJ opportunity in Amsterdam', 'DJ needed listings Amsterdam', and 'I am a DJ looking for work in Amsterdam' all use search_open_calls with portalId='dj' and location='Amsterdam'. Explicit wording such as 'post/find/search open calls' always uses this tool, even when the speaker is a venue manager or private event host. Impersonal posted requirements such as 'analog listening sessions looking for organisers' also use this tool. Do NOT use this as the first choice when a buyer says 'I need/find/want to hire/book a DJ or live band'; call search_availability for that buyer-side intent instead. Venues and event hosts post open calls to find DJs, live bands, comedians, artists, content creators, event crew, solopreneurs, game hosts, casting talent, and more. Returns structured listings with location, genre, type, close date, and a canonical URL. Each result includes allowedResponderRoles so callers can explain who may apply through the listing's canonical web page. All results are PII-free.

Use this first for buyer-side requests to find, hire, or book talent, crew, suppliers, or services: 'I need a live band in St Kilda', 'find a DJ near Amsterdam', or 'event crew for hire'. For 'I need a live band in St Kilda', use portalId='lb-availability' and location='St Kilda'. Location hierarchy allows broader Melbourne availability to match St Kilda and labels it as a parent-area match. Do NOT use this when the speaker is the talent seeking work, e.g. 'I am a DJ looking for gigs/work'; use search_open_calls for that perspective. Do NOT use this when the user explicitly says 'open call' or asks to post/find/search open calls; that explicit wording takes priority. If availability returns zero, offer to post an open call; never claim a match exists. Search availability listings posted by performers, crew, and service providers who are actively seeking bookings. These are the supply side of the platform — DJs, bands, comedians, artists, event crew, and more advertising their availability for a date range or location. Complement to search_open_calls (demand side).

Use when the user asks to find, show, attend, watch, visit, or buy tickets for an event or session—not when they need to hire talent. For example, 'find an analogue listening session in Melbourne' uses this tool; 'analogue listening sessions looking for organisers' uses search_open_calls. Search first-party upcoming live events submitted directly to the Open Call Portals Live Events Map. Includes DJ sets, live bands, comedy nights, and more with geo coordinates (lat/lng), ticketing info, source links, and event start/end times. All events are future or currently in progress.

Look up one opportunity by its exact public UI reference (for example DJ-3128) before making any claim about it. Returns only an active, non-deleted, non-membership, non-partner public listing and its allowedResponderRoles. State only fields in the live result; missing means not provided. Never invent volume, frequency, or competition.

Validate a versioned, allowlisted listing-form prefill and return the canonical create-form URL. It supports every mounted form advertised by get_platform_schema (39 portal forms plus live events); the exact portal-specific fields, posting roles, and value shapes are declared in this tool's schema. This is a no-write handoff: it never creates a draft, sends email, verifies a code, or publishes. Do not include email addresses, verification codes, tokens, session IDs, credentials, contact data, or unrecognized fields.

無需輸入參數。

For an exact active DJ opportunity only, validate a small response prefill and return the normal editable DJ form URL. This is a no-write handoff: AI may prepare it, but the human supplies identity/contact, consent and verification, then clicks send. It never creates drafts, sends email, verifies, publishes, creates alerts, or uses webhooks. Do not include names, email, phone, credentials, tokens, consent, verification codes, or submission fields.