Skip to main content
Glama

generate_ugc

Generate authentic, smartphone-style user-generated content images for marketing, reviews, unboxings, and testimonials that look natural and relatable, not AI-generated.

Instructions

Generate authentic user-generated content style images that look natural, relatable, and not AI-generated.

Use this when:

  • Creating UGC-style content for marketing campaigns

  • Need authentic, smartphone-quality aesthetic

  • Want relatable, casual content that connects with audiences

  • Creating unboxing, lifestyle, review, or testimonial-style visuals

  • Need diverse, realistic scenarios (home, cafe, gym, outdoor, etc.)

NOT for:

  • Polished product photography (use generate_product instead)

  • Professional social media graphics (use generate_social_media instead)

  • Logos or branding assets (use generate_logo instead)

  • Editing existing UGC images (use edit_image instead)

Chain with: If user requests specific pixel dimensions, chain with resize_image after generation.

Example: "generate_ugc description='person enjoying morning coffee' scenario='lifestyle' setting='home'"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "description": "<description>",
      "outputFormat": "<outputFormat>"
    },
    "name": "generate_ugc"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNo
settingNo
platformNo
scenarioNo
descriptionYes
outputFormatYespng
outputFilenameNo
productInSceneNo
demographicHintsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the aesthetic intent and the down-stream chaining behavior, which is genuinely useful, but says nothing about cost, latency, return shape (no output schema exists), or whether generation is synchronous or queued. For an expensive generative call with zero annotation coverage, these omissions are notable.

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?

The front-loaded summary sentence followed by 'Use this when' / 'NOT for' / 'Chain with' sections makes it scannable and every block has a clear job. The closing example is slightly redundant with the enum documentation but earns its place as the only parameter guidance present.

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

Completeness3/5

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

Routing and selection are exceptionally well covered, so an agent knows when to reach for this tool. However, with 9 parameters at 0% schema description coverage and no output schema, an agent still lacks the semantics to fill in mood, platform, productInScene, or demographicHints correctly, leaving the definition half-complete for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, and the description only illustrates three of them (description, scenario, setting) via a single example line. Parameters like mood, platform, productInScene, demographicHints, and outputFilename receive no explanation of effect at all, so the description does not compensate for the coverage gap.

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 opens with a specific verb+resource ('Generate authentic user-generated content style images') and adds a differentiating qualifier ('look natural, relatable, and not AI-generated') that separates it from polished-image siblings. An agent can immediately tell this apart from generate_product or generate_logo.

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?

It has an explicit 'Use this when' list and an explicit 'NOT for' list naming all four relevant alternatives (generate_product, generate_social_media, generate_logo, edit_image) with the condition that selects each. It also names a follow-on chain (resize_image) for pixel dimensions, which is unusually complete routing guidance.

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