Skip to main content
Glama

Make a trend video or photo

run_template
Destructive

Make a MakeViral trend video or photo from the user's photos. It spends the version's credits from the user's MakeViral account (a failed run gives them all back). A photo is usually ready in this call and the result has the link. A video takes a few minutes: then call get_run with wait true until it is ready, and give the user the link. Before calling: 1) pick the template and version with get_template, 2) tell the user the price in credits, 3) ask for exactly the photos that version needs, in its order, 4) ask the user to confirm the people in the photos are them or people who agreed, and that no one in them is a child. Photos: pass the files the user attached in this chat as photos, OR public image links as photoUrls, OR an uploadId from create_upload_link when the user cannot attach files here. Never use photos of a public figure or of someone who did not agree. When the account can pay, the photos are checked before the charge: a blurry, dark or low-resolution photo, a small or missing face, a group photo in a one-person slot, more than one animal in a one-pet slot, or a person in a pet slot returns an explanation and charges nothing. Then ask for a better photo, or for the user's OK to go on with acceptLowQualityPhoto.

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": {
      "template": "<template>",
      "photosConsent": "<photosConsent>"
    },
    "name": "run_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional 'make it yours' values: one { id, value } per field id that get_template lists
objectNoKnight sword swap only: the object one knight hands the other
photosNoThe user's photos attached in the chat, in the version's photo order
qualityNoQuality option id from get_template. Default: the template's default option (listed first).
versionNoVersion id from get_template. Default 'main'.
templateYesTemplate slug, e.g. 'knight-cat-ai-video'
uploadIdNoThe id from create_upload_link, after the user added the photos there
photoUrlsNoPublic https links to the photos (JPEG, PNG or WebP), in the version's photo order
requestIdNoOptional id (8-64 letters, digits, - or _). The same id never charges twice. Without it, the same request within 10 minutes returns the first run; pass a new id to make it again with the same photos.
photoSubjectsNoOptional: what a photo shows when it is NOT a person (a pet or animal, a robot, toy or cartoon character, or something else). The video keeps that one's own body and look, and the face check does not ask for a face on it. No consent is needed for this.
photosConsentYestrue only after the user confirmed that everyone in the photos is the user or agreed to it, and that no one is a child
acceptLowQualityPhotoNoOnly after this tool said a photo has a quality problem: true when the user chose to go on with these photos and agreed that MakeViral is not responsible for results caused by photo quality and gives no refund for them. Leave it out otherwise.

Output Schema

NameRequiredDescriptionDefault
runYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / acceptLowQualityPhoto
      Added value: +{
      +  "description": "Only after this tool said a photo has a quality problem: true when the user chose to go on with these photos and agreed that MakeViral is not responsible for results caused by photo quality and gives no refund for them. Leave it out otherwise.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / photoSubjects
      Added value: +{
      +  "description": "Optional: what a photo shows when it is NOT a person (a pet or animal, a robot, toy or cartoon character, or something else). The video keeps that one's own body and look, and the face check does not ask for a face on it. No consent is needed for this.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "photo": {
      +        "description": "1 = the first photo",
      +        "maximum": 4,
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "subject": {
      +        "enum": [
      +          "person",
      +          "animal",
      +          "character",
      +          "other"
      +        ],
      +        "type": "string"
      +      },
      +      "what": {
      +        "description": "Optional: what it is in the user's words, e.g. 'golden retriever' or 'red robot toy'",
      +        "maxLength": 40,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "photo",
      +      "subject"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 4,
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / run / properties / saveUrl
      Added value: +{
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • removedInput schema / properties / fields / additionalProperties
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / fields / description
      Previous value: -"Optional 'make it yours' values by field id (get_template lists them)"New value: +"Optional 'make it yours' values: one { id, value } per field id that get_template lists"
    • addedInput schema / properties / fields / items
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "value": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "value"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / fields / maxItems
      Added value: +20
    • changedInput schema / properties / fields / type
      Previous value: -"object"New value: +"array"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say destructive/openWorld/non-idempotent; the description adds the real cost model (spends version credits, full refund on failure), the pre-charge quality gate with the specific failure classes that return an explanation and charge nothing, the consent/no-minors policy, the 10-minute requestId dedupe window, and video latency expectations. What gets destroyed and when money moves are both stated, which is exactly what destructiveHint cannot convey.

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-loads the outcome and cost, then the timing branch, then the pre-call checklist, then input mechanics, then the quality path — a sensible order for a 12-parameter tool. It is dense and the public-figure/no-consent warning partly repeats the consent confirmation step, so a sentence could be trimmed, but nothing is filler.

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 12-parameter, nested-object, destructive, credit-spending tool, the description covers cost, refunds, latency, polling handoff, consent, photo source selection, and the low-quality retry loop. An output schema exists, so return-shape explanation is properly omitted.

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%, so the baseline is 3; the description earns extra by explaining ordering semantics for photos/photoUrls, that photoSubjects exempts non-person subjects from the face check and needs no consent, and that acceptLowQualityPhoto is only valid after a quality rejection. It adds marginal meaning beyond the schema rather than duplicating it, though fields/object/quality details are left to the schema.

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?

Opens with a specific verb+resource: make a MakeViral trend video or photo from the user's photos. It immediately differentiates itself from get_run, get_template and create_upload_link by casting them as prerequisites, so an agent knows this is the terminal generation call.

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?

Gives an explicit numbered pre-call sequence (pick template via get_template, quote the credit price, request the exact photos in version order, confirm consent), then branches on output type: photo finishes in-call, video requires polling get_run with wait true. It also enumerates three mutually exclusive photo-input paths (attached files, photoUrls, uploadId from create_upload_link) with the condition that selects each.

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.

Resources