Skip to main content
Glama

adpanel_synthesize_broadcast_asset

Synthesize a broadcast-ready asset from an orchestrated cinematic timeline reference, choosing format, profile, and resolution for delivery.

Instructions

Synthesize a broadcast-ready asset from an orchestrated timeline routing reference.

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": {
      "sessionId": "<sessionId>",
      "timelineRef": "<timelineRef>",
      "output": "<output>"
    },
    "name": "adpanel_synthesize_broadcast_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYesBroadcast output envelope
sessionIdYesActive orchestration session identifier
timelineRefYesRouting reference returned from orchestrate_cinematic_timeline
publishTargetsNoOptional downstream publish target identifiers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether synthesis is a long-running or asynchronous job, whether it must be polled, whether supplying publishTargets triggers immediate downstream publication, or whether existing assets are overwritten. Only "broadcast-ready" hints at quality expectations.

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?

A single well-formed sentence with no filler and the key noun phrase front-loaded. It is efficient, though arguably too terse for the operation it describes.

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

Completeness2/5

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

This is a complex, nested-parameter synthesis operation with no annotations and no output schema, so the description is the only place to explain job behavior and what comes back. It omits execution model, expected return (asset reference? job id?), and the effect of publishTargets, leaving significant gaps.

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 all four parameters (sessionId, timelineRef, output envelope with format/profile/resolution, publishTargets) are already documented in the schema, establishing a baseline of 3. The description adds only the general notion of a "routing reference" and does not clarify profile routing behavior or what publish targets do.

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?

The description states a specific verb and resource — "Synthesize a broadcast-ready asset" — plus the input source, an "orchestrated timeline routing reference", which links it to the orchestrate step. It does not explicitly name the sibling tools, but the synthesis-versus-ingest-versus-orchestrate distinction is inferable.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "orchestrated timeline routing reference" hints that this runs after a timeline has been orchestrated, and the timelineRef schema description confirms it comes from orchestrate_cinematic_timeline. There is no explicit when-to-use/when-not wording, no mention of preconditions, and no guidance on when publishTargets should be supplied.

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