Skip to main content
Glama

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_generate_ad

Ad Studio: turns a product photo into a finished ad (20 credits). graphic = product alone in a styled scene; product = a creator holding it; service = a creator with no product. Pick templateId with fattly_list_ad_presets. Upload the product photo with fattly_upload_image first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesgraphic = product only (needs productImageUrl). product = creator + product (needs productImageUrl AND a creator). service = creator only (needs prompt AND a creator).
promptNoWhat the ad is about — REQUIRED for service mode. Any language; it is translated to English server-side.
actorIdNoId of an avatar you generated earlier on this account („My actors”).
consentNoREQUIRED (true) when you pass avatarUrl (your own creator photo). Must be true. By setting it you confirm that you have the rights to, and the consent of, every person who is visible or audible in the materials you provide.
settingNoScene id from fattly_list_ad_presets (scenes).
avatarIdNoCreator from the built-in roster (product/service modes). See fattly_list_ad_presets.
avatarUrlNoYour own creator photo as a fal URL (alternative to avatarId). Using a photo of a real person requires consent: true.
unbrandedNoKeep the product free of invented logos/branding.
templateIdNoAd preset id from fattly_list_ad_presets. Must match the mode (graphic presets only in graphic mode, and vice versa).
aspectRatioNoGraphic mode only: 1:1, 2:3, 9:16 or 16:9 (default 1:1). Ignored in product/service modes, which are always 9:16.
productImageUrlNoProduct photo as a fal URL — REQUIRED for graphic and product modes. Get one with fattly_upload_image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / avatarUrl / description
      Previous value: -"Your own creator photo as a fal URL (alternative to avatarId)."New value: +"Your own creator photo as a fal URL (alternative to avatarId). Using a photo of a real person requires consent: true."
    • addedInput schema / properties / consent
      Added value: +{
+  "description": "REQUIRED (true) when you pass avatarUrl (your own creator photo). Must be true. By setting it you confirm that you have the rights to, and the consent of, every person who is visible or audible in the materials you provide.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-idempotent, non-destructive write. The description adds the elements annotations can't: the 20-credit cost and the required upstream sequence (upload image, list presets). It does not explain what the generated artifact looks like or how it is returned, so it is not a full 5.

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 core purpose and cost, then modes, then prerequisites — dense and mostly free of padding. The mode-list sentence is somewhat redundant with the enum, costing it the top score.

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

Completeness4/5

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

For an 11-parameter generative tool with no output schema, it covers cost, mode semantics, prerequisites, and where to get templateId, which is what an agent needs to invoke it correctly. Return-value details are the only meaningful gap, and the description never overreaches into what it can't guarantee.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter, including the mode enum and its dependencies. The description's mode gloss largely restates the enum definition, adding no syntax or format detail beyond it — the baseline 3.

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 concrete verb and resource ('turns a product photo into a finished ad') under a named product area ('Ad Studio'), and immediately distinguishes the three modes. An agent can tell this apart from fattly_generate_image or fattly_generate_ad_video from the description alone.

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?

Gives explicit workflow ordering — pick templateId with fattly_list_ad_presets and upload the product photo with fattly_upload_image first — plus the mode-selection rule (graphic/product/service). It stops short of naming when to prefer the video sibling, so it is clear context rather than full when/when-not coverage.

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

All Fattly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources