Skip to main content
Glama

create_creator_profile

Idempotent

Create an owned, versioned creator profile. Free; admin scope.

    At least one creator/audience/stance/fact is required. Returns the exact version,
    deny-by-default secondary-use decisions, receipts, and an unverified-attestation
    warning. Optional idempotency_key replays safely. Errors: unauthorized, forbidden,
    invalid_request, conflict, idempotency_conflict, configuration_unavailable, rate_limited.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stanceNoOptional: what the creator is for or against, selling, or building, so hooks carry a real position instead of a neutral summary.
api_keyNoAPI key for this call. Omit to fall back to the Authorization: Bearer / X-API-Key request header (streamable-HTTP only), then the VHGENGINE_API_KEY env var (the stdio default). No key resolvable -> unauthorized.
creatorNoOptional: who is speaking, free text ('wedding videographer, 40k followers, I talk to camera over b-roll of my shoots'). The more the engine knows about the creator, the more the hooks are theirs rather than a generic narrator's.
audienceNoOptional: who watches ('engaged couples budgeting'). Aims every hook at a real audience instead of an assumed one.
display_nameYesAccount-local profile label, 1-100 characters.
secondary_useNoEach secondary-use decision is independent and denied by default. These decisions are retained for governance only: generation, scoring, retrieval, and learning do not consume them today.
idempotency_keyNoCaller-chosen replay key (any string, unique per intended effect). A repeat call with the SAME key returns the stored result and is NEVER charged twice; the same key with different arguments is an idempotency_conflict. Omit and every call is a fresh, separately charged operation.
authority_attestedYesI confirm that I am this creator or am authorized by them to store these declarations and use the selected immutable version when I later make an explicit profile-bound hook-generation request. VHGENGINE records this caller attestation; it does not verify identity, ownership, or legal authority.
first_person_factsNoOptional: facts TRUE of this creator that hooks may assert first-person ('I have filmed 200+ weddings'). The ONLY sanctioned source of personal claims; without it, hooks never invent a biography.
subject_relationshipYesself, authorized representative, or organization representative.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stanceNoCaller-declared speaker stance.
creatorNoCaller-declared creator description.
versionNoExact immutable version returned by this read or write.
audienceNoCaller-declared audience.
replayedNotrue when idempotency replayed the stored write.
created_atNoProfile creation time, ISO-8601 UTC.
is_currentNoWhether this immutable version is current.
profile_idNoOpaque account-owned profile id.
updated_atNoCurrent profile update time, ISO-8601 UTC.
display_nameNoAccount-local profile label.
secondary_useNoThree independent deny-by-default decisions.
current_versionNoProfile's current version.
attestation_noteNoUnverified-authority and non-consumption warning.
consent_receiptsNoLatest revision receipt for every decision.
authority_attestedNoThe caller recorded the required authority attestation.
first_person_factsNoSanctioned caller-declared facts.
rights_notice_textNoExact immutable caller-authority notice text.
version_created_atNoThis version's creation time, ISO-8601 UTC.
consent_notice_textNoExact deny-by-default secondary-use notice text.
subject_relationshipNoCaller's declared relationship to the creator.
rights_notice_versionNoImmutable rights-attestation notice version.

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses multiple behavioral traits beyond the idempotentHint annotation: it returns 'the exact version, deny-by-default secondary-use decisions, receipts, and an unverified-attestation warning' and lists specific error codes. It also explains idempotency_key replays safely, adding meaning to the annotation.

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?

The description is compact and front-loaded with the key purpose. All sentences add value: cost/scope, validation requirement, return values, idempotency, and error list. The error list is concise and the overall structure is efficient without redundancy.

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?

Given the tool's complexity (10 parameters, output schema, annotations), the description covers essentials: cost, permissions, minimum content, return payload, idempotency behavior, and errors. It complements the rich schema without repeating it, providing sufficient context 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 coverage is 100%, but the description adds a crucial cross-parameter constraint: 'At least one creator/audience/stance/fact is required,' which is not evident from individual optional fields. It also highlights idempotency_key replay safety, supplementing the schema's description.

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 clearly states 'Create an owned, versioned creator profile' with a specific verb and resource. It distinguishes the create operation from sibling tools like update_creator_profile, delete_creator_profile, and list_creator_profiles by focusing on creation and the 'owned, versioned' aspect.

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?

The description provides clear context: 'Free; admin scope' indicates cost and permission prerequisites, and 'At least one creator/audience/stance/fact is required' gives a content constraint. It also notes optional idempotency_key replay safety. It doesn't explicitly name alternatives, but the create-vs-update distinction is clear from context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, e.g., signup vs. delete_account, create_key vs. revoke_key, generate_hooks vs. score_hook. Even similar tools like generate_hooks and generate_hooks_batch are clearly differentiated by single vs. batch operation.

Naming Consistency5/5

All 32 tools use a consistent verb_noun snake_case pattern (e.g., add_credits, create_checkout, revoke_key, list_outcomes) with no mixing of camelCase or other conventions.

Tool Count4/5

32 tools is slightly above the typical 15-tool range, but the domain is broad (account, keys, webhooks, generation, scoring, jobs, outcomes), and each tool has a specific purpose. No tools seem redundant.

Completeness4/5

The tool surface covers most lifecycle operations: CRUD for accounts/keys/webhooks, generation/scoring with batch and async variants, outcomes reporting, and auxiliary tools. Missing explicit delete for hooks (expire automatically) and some update operations, but no critical gaps.

Resources