Skip to main content
Glama

Write 3 scripts

write_scripts

Write three scripts for a UGC video of a product, to read before making one. Say It Again's own writer writes them from the product read_product read, held to its facts. Free, and counted against the calls get_balance gives as scripts_left. Answers an id at once: call get_scripts with it about once a minute until its status is ready or failed.

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": {
      "product": "<product>"
    },
    "name": "write_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
adNoAn ad to build the video like, its moves made for this product: a link of an ad in the Meta Ad Library, an ad's id from that library or from list_ads, which lists TikTok's ads too, or one of the team's own videos as v- and its id from get_video, with - and its part after for any but its first. A Meta Ad Library link not seen before is looked up in that library and counted against the team's ad links of the day. Not with lines or script_id.
keepNoWhat to keep of the ad: structure, the default, or pacing, its pace and its shots alone.
sizeNoThe shape the video is filmed in. 9:16 is the default.
angleNoThe angle the video argues: auto, the default, or one of the angle ids read_product lists for the product. Not with lines, script_id or ad, which argue their own.
linesNoLines for the presenter to say, one a shot: 3 to 5 for a 15-second video, up to 10 for 30 seconds. They are said word for word as sent, not translated, and read by no check of ours. With script_id they replace that script's lines in order. Every person in the ads we make, on camera or heard as a voice, is made by AI and is not a customer. Nothing in an ad may present them as someone who has used the product, because that is a fake testimonial and the law forbids it. So they have no past with it: no time spent with it, no result it has had on their own body, home, pet or life, no before and after of their own, no having bought it, and no job, family role or other identity that makes them sound like a real customer. What they have is the moment: showing the product, using it on camera and reacting to what it does there, saying what it is and what it does, and the facts the product page gives.
commentNoFor comment_reply alone: the comment the video answers, shown over its first shot. No price, link, email address, @ handle or phone number.
productYesThe product's id from read_product, or the product's link.
qualityNofast, the default, uses Seedance 2.0 mini for trying ideas; best uses Wan 3.0 for the videos the team publishes; priority uses Wan 3.0 Prime, first in our line, at a higher price of its own, refused while it is not offered. seedance25 selects Seedance 2.5 explicitly, independent of the model used by best. Send these quality values, not model names.
secondsNoThe length: fast videos are 15 seconds, best and priority videos 15 or 30 seconds.
captionsNoCaptions of what is said, on screen. On by default.
languageNoThe language the video is spoken in. Left out, the team's ad language. Arabic, Hungarian and Japanese require quality best or priority.
commenterNoFor comment_reply alone: the name of whoever wrote the comment. No link, email address or phone number.
placementNoWhere the product is in the video. auto by default.
presentersNoPresenter ids from list_presenters. Left out, one is chosen for the product.
resolutionNoThe resolution it is filmed in, a higher one at a higher price: 480p or 720p for fast; 480p, 720p or 1080p for best and priority while 1080p is offered, one not offered being refused with the ones that are. Left out, the one its scripts were written for where script_id names them, else 480p while the team's balance is its free videos, else 720p. An Arabic video whose voice is added after filming is filmed in 720p whatever is asked. quote_video says which.
video_typeNoThe kind of video, as the app's Video type, everyday by default: everyday, a plain ad; creator_review, a review filmed to the camera, as people review a product on their own channel; unboxing, the product taken out of a plain box and used for the first time; street_interview, an interviewer heard but not seen hands the person the product; podcast, two people talk at a table until the product comes into it; get_ready, using it is one step of getting ready; tutorial, how it is used, a numbered step a shot; three_things, three things about it, one after another; asmr, slow close shots of the sounds it makes, the person whispering; crush_test, one stress test on camera that harms nobody; giant_product, the product as big as a house in a real place; hidden_camera, filmed as if by a hidden camera, the person talking to themselves; comment_reply, the person answers a comment shown on the video. A type is refused where its placement or language does not suit it, and with lines, ad, angle or script_id, which make the video's shape themselves.
descriptionNoDescribe the video: where it happens, what happens and the point it gets across. Words it gives someone to say, in quotes or not, are said as written and follow the rule given for lines.
video_styleNocasual (the default), professional or energetic.
second_presenterNoFor podcast alone: the other person at the table, one of our own presenters by its id from list_presenters, not one the team described. Left out, one is chosen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / quality / description
      Previous value: -"fast, the default, uses Seedance 2.0 mini for trying ideas; best uses Wan 3.0 for the videos the team publishes; priority uses Wan 3.0 Prime, first in our line, at a higher price of its own, refused while it is not offered. Send these quality values, not model names."New value: +"fast, the default, uses Seedance 2.0 mini for trying ideas; best uses Wan 3.0 for the videos the team publishes; priority uses Wan 3.0 Prime, first in our line, at a higher price of its own, refused while it is not offered. seedance25 selects Seedance 2.5 explicitly, independent of the model used by best. Send these quality values, not model names."
    • changedInput schema / properties / quality / enum
      Previous value: -[
      -  "fast",
      -  "best",
      -  "priority"
      -]New value: +[
      +  "fast",
      +  "best",
      +  "priority",
      +  "seedance25"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"The language the video is spoken in. Left out, the team's ad language."New value: +"The language the video is spoken in. Left out, the team's ad language. Arabic, Hungarian and Japanese require quality best or priority."
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "en-us",
      -  "ar-eg",
      -  "ar-ae",
      -  "ar-lb",
      -  "ar",
      -  "ar-ma",
      -  "cs",
      -  "da",
      -  "nl-be",
      -  "nl",
      -  "en-au",
      -  "en-gb",
      -  "fi",
      -  "fr-ca",
      -  "fr",
      -  "de-at",
      -  "de",
      -  "de-ch",
      -  "id",
      -  "it",
      -  "no",
      -  "pl",
      -  "pt-br",
      -  "pt",
      -  "ro",
      -  "es-ar",
      -  "es-419",
      -  "es-mx",
      -  "es",
      -  "sv",
      -  "tr"
      -]New value: +[
      +  "en-us",
      +  "ar-eg",
      +  "ar-ae",
      +  "ar-lb",
      +  "ar",
      +  "ar-ma",
      +  "cs",
      +  "da",
      +  "nl-be",
      +  "nl",
      +  "en-au",
      +  "en-gb",
      +  "fi",
      +  "fr-ca",
      +  "fr",
      +  "de-at",
      +  "de",
      +  "de-ch",
      +  "hu",
      +  "id",
      +  "it",
      +  "ja",
      +  "no",
      +  "pl",
      +  "pt-br",
      +  "pt",
      +  "ro",
      +  "es-ar",
      +  "es-cl",
      +  "es-co",
      +  "es-419",
      +  "es-mx",
      +  "es",
      +  "sv",
      +  "tr"
      +]
    • changedInput schema / properties / quality / description
      Previous value: -"fast, the default, for trying ideas; best, for the videos the team publishes; or priority: best made sooner, first in our line, at a higher price of its own, refused while it is not offered."New value: +"fast, the default, uses Seedance 2.0 mini for trying ideas; best uses Wan 3.0 for the videos the team publishes; priority uses Wan 3.0 Prime, first in our line, at a higher price of its own, refused while it is not offered. Send these quality values, not model names."
  3. Changed10 schema fields changed
    • changedInput schema / properties / ad / description
      Previous value: -"An ad to build the video like, its moves made for this product: a link of an ad in the Meta Ad Library, an ad's id from list_ads or the library, or one of the team's own videos as v- and its id from get_video, with - and its part after for any but its first. A library link not seen before is looked up in the library and counted against the team's ad links of the day. Not with lines or script_id."New value: +"An ad to build the video like, its moves made for this product: a link of an ad in the Meta Ad Library, an ad's id from that library or from list_ads, which lists TikTok's ads too, or one of the team's own videos as v- and its id from get_video, with - and its part after for any but its first. A Meta Ad Library link not seen before is looked up in that library and counted against the team's ad links of the day. Not with lines or script_id."
    • addedInput schema / properties / comment
      Added value: +{
      +  "description": "For comment_reply alone: the comment the video answers, shown over its first shot. No price, link, email address, @ handle or phone number.",
      +  "maxLength": 180,
      +  "type": "string"
      +}
    • addedInput schema / properties / commenter
      Added value: +{
      +  "description": "For comment_reply alone: the name of whoever wrote the comment. No link, email address or phone number.",
      +  "maxLength": 30,
      +  "type": "string"
      +}
    • changedInput schema / properties / description / maxLength
      Previous value: -600New value: +2000
    • changedInput schema / properties / quality / description
      Previous value: -"fast (the default) or best."New value: +"fast, the default, for trying ideas; best, for the videos the team publishes; or priority: best made sooner, first in our line, at a higher price of its own, refused while it is not offered."
    • changedInput schema / properties / quality / enum
      Previous value: -[
      -  "fast",
      -  "best"
      -]New value: +[
      +  "fast",
      +  "best",
      +  "priority"
      +]
    • addedInput schema / properties / resolution
      Added value: +{
      +  "description": "The resolution it is filmed in, a higher one at a higher price: 480p or 720p for fast; 480p, 720p or 1080p for best and priority while 1080p is offered, one not offered being refused with the ones that are. Left out, the one its scripts were written for where script_id names them, else 480p while the team's balance is its free videos, else 720p. An Arabic video whose voice is added after filming is filmed in 720p whatever is asked. quote_video says which.",
      +  "enum": [
      +    "480p",
      +    "720p",
      +    "1080p"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / second_presenter
      Added value: +{
      +  "description": "For podcast alone: the other person at the table, one of our own presenters by its id from list_presenters, not one the team described. Left out, one is chosen.",
      +  "type": "string"
      +}
    • changedInput schema / properties / seconds / description
      Previous value: -"The length: fast videos are 15 seconds, best videos 15 or 30 seconds."New value: +"The length: fast videos are 15 seconds, best and priority videos 15 or 30 seconds."
    • addedInput schema / properties / video_type
      Added value: +{
      +  "description": "The kind of video, as the app's Video type, everyday by default: everyday, a plain ad; creator_review, a review filmed to the camera, as people review a product on their own channel; unboxing, the product taken out of a plain box and used for the first time; street_interview, an interviewer heard but not seen hands the person the product; podcast, two people talk at a table until the product comes into it; get_ready, using it is one step of getting ready; tutorial, how it is used, a numbered step a shot; three_things, three things about it, one after another; asmr, slow close shots of the sounds it makes, the person whispering; crush_test, one stress test on camera that harms nobody; giant_product, the product as big as a house in a real place; hidden_camera, filmed as if by a hidden camera, the person talking to themselves; comment_reply, the person answers a comment shown on the video. A type is refused where its placement or language does not suit it, and with lines, ad, angle or script_id, which make the video's shape themselves.",
      +  "enum": [
      +    "creator_review",
      +    "everyday",
      +    "unboxing",
      +    "street_interview",
      +    "podcast",
      +    "get_ready",
      +    "tutorial",
      +    "three_things",
      +    "asmr",
      +    "crush_test",
      +    "giant_product",
      +    "hidden_camera",
      +    "comment_reply"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, consistent with script generation. The description adds non-obvious operational context: the call is free but consumes scripts_left from get_balance, returns an id immediately, and must be polled through get_scripts about once a minute until ready or failed.

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 description is three sentences and front-loads the purpose, then cost/quota, then async return behavior. It is dense but every sentence adds operational value; the only minor cost is awkward phrasing such as 'the product read_product read.'

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 19-parameter generation tool with no output schema, the description covers the critical workflow: read_product input, script quota, returned id, and get_scripts polling. The schema itself details all parameter constraints, so nothing essential is missing for correct invocation.

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% across 19 parameters, so the schema already documents enums, defaults, constraints, and interaction rules. The description references product, read_product, and the get_balance quota but adds no parameter syntax or semantics beyond those structured fields, so the baseline of 3 applies.

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 states a specific verb and resource: 'Write three scripts for a UGC video of a product.' It also identifies the grounding source, the product read via read_product, and distinguishes the script-writing step from later video-making and polling.

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?

It says to use this before making a video and names read_product as the prerequisite plus get_scripts as the polling follow-up. It does not explicitly name make_video as the alternative or state when not to use it, but the workflow context is clear.

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.