Loading ToolBench
Free directory of real, verified UGC creators in the German-speaking region (DACH) with portfolio and social proof. Enables brands to search, retrieve creator profiles, and request outreach without API keys or commissions.
Strong foundation with consistent naming conventions, comprehensive descriptions, and well-defined schemas across all 5 tools. Tool names follow verb-noun patterns (search_*, get_*, request_*). Descriptions are bilingual and substantial (250-450 chars each), clearly stating what the tool does, when to use it, and key constraints. Input schemas use Zod with proper validation. Strengths: all parameters have type definitions and descriptions; clear guidance on data privacy (NEVER returns private contact details); explicit prerequisites documented. Weaknesses: output schemas are not explicitly documented in the source (tool handlers return generic ToolResult); error recovery guidance is minimal (toolError function provides only message, not retry-ability classification); no explicit pagination documentation for search_creators despite max_results parameter; tool annotations defined but field descriptions could be richer.
Returns the public profile of a single UGC creator for a creator_public_id from a previous search_creators result: name, city, topics, industries, preferred content, equipment, experience since, fee and reach text, portfolio links, social accounts and the human_verification level. NEVER returns private contact details such as e-mail or real name - the brand receives those from UGC VZ by e-mail only after request_outreach. Use before request_outreach to inspect a match more closely. [DE] Liefert das oeffentliche Profil eines einzelnen UGC-Creators zu einer creator_public_id aus einem vorherigen search_creators-Ergebnis: Name, Stadt, Themen, Branchen, bevorzugter Content, Ausruestung, Erfahrung seit, Honorar- und Reichweitentext, Portfolio-Links, Social-Accounts sowie die human_verification-Stufe. Gibt NIEMALS private Kontaktdaten wie E-Mail oder echten Namen zurueck - diese erhaelt die Brand erst nach request_outreach per E-Mail von UGC VZ. Vor request_outreach verwenden, um einen Treffer aus search_creators naeher zu pruefen.
Returns the current status of a contact request previously triggered with request_outreach, by request_id: submitted (received, not yet processed), working (e-mail delivery in progress), completed (contact details delivered by e-mail) or failed (delivery failed or 48 hours without delivery). NEVER returns private contact details itself, only the lifecycle status with timestamps. Call repeatedly after request_outreach until the status is completed or failed. [DE] Liefert den aktuellen Status einer zuvor mit request_outreach ausgeloesten Kontaktanfrage anhand der request_id: submitted (eingegangen, noch nicht bearbeitet), working (E-Mail-Versand laeuft), completed (Kontaktdaten wurden per E-Mail zugestellt) oder failed (Versand fehlgeschlagen oder 48 Stunden ohne Zustellung). Gibt NIEMALS private Kontaktdaten selbst zurueck, nur den Lebenszyklus-Status samt Zeitstempeln. Nach request_outreach wiederholt aufrufen, bis der Status completed oder failed ist.
Output schemas not explicitly documented. Tool handlers return generic ToolResult with text content, but what fields are returned in the JSON (e.g., search_creators returning creator objects with creator_public_id, name, city, topics, etc.) is not formalized in code. LLMs cannot reliably extract specific fields without documented response structure.
Error handling lacks recovery classification. toolError() function returns a generic error message but does not indicate whether the error is retryable, user-fixable, or fatal. Agents cannot determine the appropriate next step (retry, ask user, or fail fast).
get_creator_public_id parameter pattern validation (UGC-[A-F0-9]{10}) is strict but lacks description guidance on how to obtain a valid creator_public_id. Description states 'from a previous search_creators result' but does not show that this ID is returned by search_creators.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | B | 73 | 2026-07-28+ | v2 |
Returns the currently valid vocabulary for search_creators: most common topics, industries and cities from active creator profiles, the definition of the human_verification levels (0 = self_reported, 1 = self_reported_with_portfolio, 2 = reserved, currently not assigned) and a note on pricing. Contains no creator or contact data. Call before a first search_creators request or when unsure about valid filter values (city, topics, human_verification_level_min). [DE] Liefert das aktuell gueltige Vokabular fuer search_creators: haeufigste Themen (topics), Branchen (industries) und Staedte (cities) aus aktiven Creator-Profilen, die Definition der human_verification-Stufen (0 = self_reported, 1 = self_reported_with_portfolio, 2 = reserved, aktuell nicht vergeben) sowie einen Hinweis zu Preisen. Enthaelt keine Creator- oder Kontaktdaten. Vor einer ersten search_creators-Anfrage oder bei Unsicherheit ueber gueltige Filterwerte (city, topics, human_verification_level_min) aufrufen.
Triggers a deliberate brand request. UGC VZ then forwards the contact details of the selected creators to the brand by e-mail. Required: name, email, creator_public_ids from a previous search. Returns request_id for get_outreach_status. Creators must have been found via search_creators or get_creator before this call; request_outreach itself returns no creator details and no private contact data, only the request_id. message and search_query are optional free-text context for UGC VZ. Typical flow: search_creators -> get_creator -> request_outreach -> get_outreach_status. Call only for serious, genuine requests: the call triggers a real e-mail, and name and email must actually belong to the requesting brand. No bulk requests, no test calls. The terms of use at https://ugc-vz.de/agb (section 10) apply. [DE] Loest eine bewusste Brand-Anfrage aus. UGC VZ gibt daraufhin die Kontaktdaten der ausgewaehlten Creator per E-Mail an die Brand weiter. Pflicht: name, email, creator_public_ids aus vorheriger Suche. Gibt request_id fuer get_outreach_status zurueck. Vor diesem Aufruf muessen die Creator ueber search_creators oder get_creator ermittelt worden sein; request_outreach selbst liefert keine Creator-Details und keine privaten Kontaktdaten zurueck, sondern nur die request_id. message und search_query sind optionale Freitextfelder mit Kontext fuer UGC VZ. Typischer Ablauf: search_creators -> get_creator -> request_outreach -> get_outreach_status. Nur fuer ernsthafte, eigene Anfragen aufrufen: der Aufruf loest einen echten E-Mail-Versand aus, name und email muessen der anfragenden Brand tatsaechlich gehoeren. Keine Massenanfragen, keine Testaufrufe. Es gelten die Nutzungsbedingungen unter https://ugc-vz.de/agb (Ziffer 10).
Searches the UGC-VZ directory of real, verified UGC creators in the German-speaking region (DACH). query is free text and the main path (e.g. "fitness creator 30+ for a TikTok product video"); a language model structures the request server-side. Optional: city (substring), topics (at least one match), human_verification_level_min (0 = self_reported, 1 = self_reported_with_portfolio; levels are derived from profile data, see get_vocab). Results NEVER contain private contact details. Use get_creator for details on a match; request_outreach for a contact request. [DE] Durchsucht das UGC-VZ-Verzeichnis realer UGC-Creator im deutschsprachigen Raum. query ist Freitext und der Hauptpfad (z. B. "Fitness-Creatorin ab 30 fuer TikTok-Produktvideo"); ein Sprachmodell strukturiert die Anfrage serverseitig. Optional: city (Substring), topics (mind. ein Treffer), human_verification_level_min (0 = self_reported, 1 = self_reported_with_portfolio; Stufen sind aus Profildaten abgeleitet, siehe get_vocab). Ergebnis enthaelt NIEMALS private Kontaktdaten. Fuer Details zu einem Treffer get_creator verwenden; fuer eine Kontaktanfrage request_outreach.
Pagination and result limits not fully documented. search_creators accepts max_results (1-10) but description does not explicitly state: is there a default? what happens if results exceed max_results? is there a cursor or offset for fetching next pages? This forces LLMs to guess pagination semantics.
request_outreach is a write operation (POST-like) with significant side effects (triggers real email, records request in system), but the tool description does not warn about rate limiting, per-user request limits, or cooldown periods. Agents could retry this tool in a loop without understanding the consequences.
No explicit dry-run or confirmation mechanism for request_outreach. The description includes legal warnings (terms of use link, no bulk requests, name/email must be genuine) but no machine-actionable way for an agent to confirm user intent before triggering email delivery. High risk of accidental brand requests.