Skip to main content
Glama

Daily Studio Teleprompter

by app.dailystudio
OverviewDiscussionsAdmin

Send script to teleprompter

send_script_to_teleprompter

Turn one or more finished video scripts into a single one-tap link that opens the user's Daily Studio app with the script(s) loaded into the teleprompter and the right platform safe-zones selected, ready to record. For one script use text; for a batch the user will record back-to-back (a day's 3-4 videos, or a whole content plan — up to 100), use scripts — they land as an in-app shoot queue in order, and ONE link carries them all. Call this only once the scripts are final. Returns a link the user taps on their iPhone; on a desktop it opens a page with a QR code to scan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wpmNoOptional scroll speed in words per minute. Sets the app's teleprompter speed. Omit to leave the user's setting alone. With `scripts`, applies to items that don't set their own.
textNoA finished talking-head script to speak directly to camera, plain UTF-8. Newlines allowed. Provide either this or `scripts`, not both.
titleNoOptional short label for `text`, e.g. 'Cold plunge hook'.
scriptsNoA batch of scripts (in recording order) delivered as a single link — up to 100 of them, 400000 characters of script in total. The app queues them; after each recording it offers the next. Provide either this or `text`, not both.
platformNoWhere the video will be published. Selects that platform's safe-zone overlay so on-screen UI never covers the creator. Omit to leave the user's choice alone. With `scripts`, applies to items that don't set their own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / scripts / items / properties / text / description
      Previous value: -"The finished script for this video, plain UTF-8."New value: +"The finished talking-head script: one hook, one idea and a short closing, plain UTF-8."
    • changedInput schema / properties / text / description
      Previous value: -"A single finished teleprompter script, plain UTF-8. Newlines allowed. Provide either this or `scripts`, not both."New value: +"A finished talking-head script to speak directly to camera, plain UTF-8. Newlines allowed. Provide either this or `scripts`, not both."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic read/write/openWorld/idempotent profile; the description adds real behavioral context beyond them: the batch becomes an ordered in-app shoot queue, one link carries all items, and the return is a tappable iPhone link or a desktop QR page. The 'only once scripts are final' constraint is also disclosed here and nowhere else.

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 purpose before mode guidance, and each sentence carries distinct information (mode choice, queue behavior, finality precondition, return format). Slightly long, but no sentence is disposable.

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 non-idempotent write tool with no output schema, the description covers the essentials: what it produces (a link / QR page), how batches behave, and the timing constraint. Nothing an agent needs to invoke it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds meaning the schema does not: which parameter to pick for single vs batch use and the fact that a batch lands as an ordered queue. It does not restate the wpm/platform inheritance rules that the schema already covers, so it stays modestly above baseline.

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 specific verb and resource (turns finished scripts into a one-tap teleprompter link) and describes the concrete outcome: scripts loaded, safe-zones selected, ready to record. It also distinguishes its two modes (`text` vs `scripts`) so an agent knows the shape of the call without reading the schema.

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 selection guidance ('For one script use `text`; for a batch the user will record back-to-back ... use `scripts`') and a precondition ('Call this only once the scripts are final'). It stops short of naming sibling tools (add_scripts_to_plan, etc.) or an explicit when-not-to-use, so it is strong context rather than full routing.

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

All Daily Studio Teleprompter 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