Skip to main content
Glama

adpanel_orchestrate_cinematic_timeline

Builds a cinematic timeline from a brand matrix routing reference, defining duration, aspect ratio, and scene count for consistent brand video orchestration.

Instructions

Orchestrate a cinematic timeline from a brand matrix 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": {
      "brandMatrixRef": "<brandMatrixRef>",
      "timeline": "<timeline>"
    },
    "name": "adpanel_orchestrate_cinematic_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYesHigh-level timeline specification
sessionIdNoOptional session identifier to chain orchestration
brandMatrixRefYesRouting reference returned from ingest_brand_matrix
narrativeBriefNoOptional creative brief for orchestration routing

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 burden of behavioral disclosure. It does not state whether orchestration creates a persistent artifact, what side effects or permissions are involved, whether the operation is synchronous or asynchronous, or how failures and partial timelines are handled.

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 a single front-loaded sentence with no filler. It is efficient, though its extreme brevity leaves important information out rather than making every word count toward completeness.

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?

For a four-parameter tool with a nested timeline object, no annotations, and no output schema, the description is too thin. It does not explain the orchestration result, success/failure behavior, or how timeline constraints interact with the brand matrix reference.

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 the schema already documents all four parameters, including the nested timeline object and its constraints. The description adds little beyond echoing that brandMatrixRef is a routing reference and does not clarify optional parameters like sessionId or narrativeBrief.

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: 'Orchestrate a cinematic timeline,' and names the input source, 'from a brand matrix routing reference.' It is distinguishable from the ingest sibling by its timeline focus, though it does not explicitly contrast itself with synthesize_broadcast_asset.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of how it should be sequenced after adpanel_ingest_brand_matrix. At most, 'from a brand matrix routing reference' implies it consumes that sibling's output, but the agent must infer the workflow.

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