UGC VZ Creator Search

get_creator

get_creator

Read-only

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`creator_public_id`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds important behavioral context: it never returns private contact details, specifies how those are delivered, and defines the scope of the public profile. Minor gaps remain around error behavior or exact response shape, but the privacy boundary is well disclosed.

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?

Front-loaded with the main verb and resource, then a comprehensive field list, followed by the privacy caveat and usage guidance. The English/German duplication nearly doubles length but is still organized and purposeful; no filler beyond that.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with no output schema, the description covers what the tool does, what it returns, where the input comes from, how to use it relative to siblings, and a critical privacy limitation. Nothing material is missing for correct invocation.

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 description coverage is 0%, so the description must compensate for the single parameter. It adds meaning by stating creator_public_id comes from a previous search_creators result, and the pattern in the schema provides the format. This is sufficient for an agent to populate the parameter correctly.

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?

States a clear verb ('Returns') and resource ('public profile of a single UGC creator'), identifies the exact input origin ('creator_public_id from a previous search_creators result'), and enumerates the returned fields. This distinguishes it from search_creators (search vs. single profile) and request_outreach.

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

Usage Guidelines5/5

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

Explicitly says to use before request_outreach to inspect a match more closely, and ties input to a previous search_creators result. It also clarifies that private contact details are not available here and surface only via request_outreach, which prevents misuse.

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

All UGC VZ Creator Search tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool occupies a distinct stage of the workflow: vocabulary lookup, searching creators, viewing a profile, requesting outreach, and checking request status. There is no functional overlap or ambiguity between the five operations.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: search_creators, get_creator, get_vocab, request_outreach, get_outreach_status. The naming convention is uniform and predictable across the entire tool set.

Tool Count5/5

Five tools is well-scoped for the stated purpose: discover UGC creators, inspect them, trigger outreach, and monitor the outcome. Each tool has a clear and necessary place in the workflow, with neither redundancy nor wasted surface area.

Completeness5/5

The tool set covers the full intended lifecycle: vocabulary guidance, search, detailed profile inspection, outreach request submission, and status polling until completion or failure. There are no obvious dead ends or missing steps for the server's stated creator-search and outreach purpose.

Resources

Need Help?