Skip to main content
Glama
Sign In
Sync MCP Server

Sync MCP Server

Official
by synchronicity-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

copy a video for edit dialogue

dialogue_upload-source
Destructive

Copies a saved video asset into Sync storage as a new video asset for an Edit Dialogue source whose URL is rejected as not hosted there. Returns the new asset ID for later dialogue tools.

Instructions

Copy a saved VIDEO asset into sync. storage as a new VIDEO asset in the given project, for an Edit Dialogue source whose URL the API rejects as not hosted in sync. storage. Usually unnecessary: dialogue-transcriptions_create makes this copy itself on that rejection and returns the copy's videoAssetId, so call this only when you need the hosted copy before or without transcribing. Not for local files (assets_create-upload-url, then assets_create) or social links (assets_create). The server downloads and re-uploads the whole video during this call (server limits, 512 MiB and 15 minutes by default) and fails if the source cannot be downloaded or is too large. Each call writes another new asset with no deduplication; it does not change the original asset and spends no generation credits. Returns asset { id, type, url }: pass asset.id as videoAssetId to every later dialogue tool. Pass projectIntent=explicit with projectId only for the project just created for this request or one the user explicitly chose; a matching name, workflow or open editor is never permission.

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject the copy is saved in: the id projects_create returned for this request (defaultWorkflow edit_dialogue), or a project the user explicitly chose.
videoAssetIdYesSaved VIDEO asset to copy, from assets_create or assets_list. Must be accessible to the connected account.
projectIntentNoRequired with projectId. Set only for an explicit user project selection/update, or the new project just created for this request. Never infer intent from a matching project name, workflow name or active editor.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.4
    • changedInput schema / properties / projectId / description
      Previous value: -"Project the Edit Dialogue work belongs to, from projects_create."New value: +"Project the copy is saved in: the id projects_create returned for this request (defaultWorkflow edit_dialogue), or a project the user explicitly chose."
    • changedInput schema / properties / videoAssetId / description
      Previous value: -"Saved VIDEO asset being edited. Use the videoAssetId dialogue-transcriptions_create returned when it made a copy."New value: +"Saved VIDEO asset to copy, from assets_create or assets_list. Must be accessible to the connected account."
  2. Changed2 schema fields changed
    • addedInput schema / properties / projectId / description
      Added value: +"Project the Edit Dialogue work belongs to, from projects_create."
    • addedInput schema / properties / videoAssetId / description
      Added value: +"Saved VIDEO asset being edited. Use the videoAssetId dialogue-transcriptions_create returned when it made a copy."
  3. Addedv0.1.5

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description explains exactly why — each call writes another new asset with no deduplication, the original is untouched, and no generation credits are spent. It adds operational facts not in the annotations: the server downloads and re-uploads the whole video, with 512 MiB / 15 minute defaults, and fails if the source is unavailable or too large.

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?

Content is front-loaded (what it does, then the usually-unnecessary warning) and every clause carries operational weight. It loses a point because the closing projectIntent sentence largely restates the schema's own const/description, which is already fully documented.

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 destructive, non-idempotent, open-world copy operation it covers prerequisites, failure modes, size/time limits, idempotency, cost, and the return shape, and even with an output schema present it names the fields returned and their downstream use. Nothing an agent needs to call 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 100%, so the baseline is 3, but the description adds cross-tool meaning: the returned asset.id must be passed as videoAssetId to every later dialogue tool, and projectIntent=explicit is required only for a just-created or explicitly chosen project, never inferred. That is semantic guidance the schema documents only locally.

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 precise verb and transformation: copy a saved VIDEO asset into sync. storage as a new VIDEO asset in a given project, with the reason (Edit Dialogue source URL rejected as not hosted in sync. storage). It also distinguishes itself from dialogue-transcriptions_create, assets_create-upload-url and assets_create, so an agent can select it without opening siblings.

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

Usage Guidelines5/5

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

Explicit when-not guidance: "Usually unnecessary: dialogue-transcriptions_create makes this copy itself... call this only when you need the hosted copy before or without transcribing." It also rules out local files and social links and points to the correct alternatives for each.

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