Skip to main content
Glama
Sign In
Foldline

Foldline

by alireza12t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Export sound cues

export_events

Exports a film page’s window.DUR and window.EV sound and cue events to JSON for mix prep, returning the file path and event count.

Instructions

Exports the page's window.DUR and window.EV (sound and cue events) to JSON for the mix. Returns the path and the number of events.

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": {
      "demo": "<demo>"
    },
    "name": "export_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoQuery string passed to the page as location.search, e.g. 'lang=en&cut=b'.
outNoDefault <demo>/events.json.
demoYesFolder that holds the film's index.html (absolute path, or relative to the library root).
sizeNoFrame size WxH, even numbers. Default 1920x1080; 1080x1920 for a vertical Short.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does say a JSON file is written and that the path and event count are returned, but it never states overwrite behavior, permission or environment requirements (the page must be loaded to read window globals), or failure modes for a tool that writes to disk.

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?

Two short sentences with the core action front-loaded and the return values immediately after. No wasted wording, though 'for the mix' is a slightly opaque qualifier that doesn't clearly earn its place.

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

Completeness3/5

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

With a fully documented 4-param schema and no output schema, the description usefully covers the return values (path and event count). However, it omits how the page is loaded and any prerequisites, which matters for a tool that executes a page and writes a file.

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 every parameter already has documented semantics. The description adds no meaning about `q`, `out`, `demo`, or `size` beyond the schema, which is acceptable at the baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: exports window.DUR and window.EV sound/cue events to JSON. That is concrete enough for an agent to distinguish it from rendering or muxing siblings. It stops short of naming an alternative or explicit scope boundaries, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus siblings such as make_subtitles or mux_audio. The phrase 'for the mix' weakly implies a downstream workflow position, but no preconditions (e.g. page must exist or be rendered first) or exclusions are stated.

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

Deploy Server

Other Tools