Skip to main content
Glama

إنشاء نص

create-script

Create a script for the signed-in user. Give it a title; naming a project is optional, and a script with no project is an ordinary script here rather than a lesser one. The script starts at the user's own default status. Send the platforms it is for in the same call rather than in a second write. Send your own rating out of ten as well — Bardiyah stores the number you send and never works one out itself. After creating the script, always add its sections, and always finish by adding one last section titled exactly \"Viral Score\" with add-script-content (that tool's description carries the required shape). Every script ends with a Viral Score section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe script title. Required.
project_idNoOptional. Which project the script belongs to, taken from a search or a listing. A script with no project is an ordinary script here, not a lesser one, and most of this user's scripts are that shape. Do not guess a project: ask, or leave it out. Left out, the script goes into the user's default project when they have set one, otherwise into no project; the reply names the project it used.
video_typeNoOptional. One of "فيديو طويل" (long form) or "فيديو قصير" (short form). Defaults to the user's default script type, long form unless they chose short.
viral_scoreNoYour rating of how likely this script is to spread, from 1 to 10. Stored exactly as sent. There is no zero: a script with no rating simply has none, and sending 0 is refused.
platform_idsNoOptional. Which platforms the script is for, taken from a listing. Only platforms this user can reach are accepted.
viral_score_reasonNoShort reasoning for the score, so the number is reviewable later.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: the new script inherits the user's default status, an omitted project_id falls back to the default project and the reply names it, only reachable platform_ids are accepted, and viral_score is stored verbatim with 0 refused. These are exactly the non-obvious side effects an agent needs before writing.

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 create action and sequences the follow-up steps in order, so it is easy to scan. It is slightly padded — the "not a lesser one" reassurance appears here and again in the schema — and the ordering advice could be tighter.

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?

Covers the full call sequence (create, add sections, close with the Viral Score section), all defaults, and even what the reply reports back despite there being no output schema. Nothing essential for a correct invocation is missing.

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 coverage is 100%, so the schema already documents every parameter, and most of the description's parameter talk (title required, project optional) restates it. It does add real meaning about viral_score being the agent's own rating that the server never computes, plus the in-call platform batching rule, but that is incremental over an already complete 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 and resource ("Create a script for the signed-in user") and implicitly scopes it against update-script and get-script by describing an initial-state creation. It also distinguishes the object itself (a script without a project is ordinary), so an agent knows exactly what is being produced.

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 clear when-and-how guidance: project naming is optional and must not be guessed, platforms belong in this same call rather than a second write, and the create must be followed by add-script-content with a final "Viral Score" section. It never states the exclusion case (modifying an existing script belongs to update-script), so it stops short of full alternative routing.

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