Skip to main content
Glama

lip_sync_video_media

Run lip sync on a video media item using a supplied audio URL. Keeps the original playable and saves the completed result as a new version when the source is still current.

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": {
      "workspaceId": "<workspaceId>",
      "mediaId": "<mediaId>",
      "modelId": "<modelId>",
      "audioUrl": "<audioUrl>"
    },
    "name": "lip_sync_video_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaIdYesVideo MediaDocV2 ID to process
modelIdYesLip-sync model ID
audioUrlYesAudio URL to drive the lip sync
videoUrlNoOverride source video URL; otherwise resolves from active media version
extraParamsNoAdditional raw V3 parameters
workspaceIdYesThe workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the operation is non-destructive ('keeps the original playable') and versioned ('saves the completed result as a new version'), with a conditional guard ('when the source is still current'). It omits async/job semantics, expected latency, and what happens if the source is no longer current.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, zero filler, with the core operation front-loaded and the versioning caveat following. Every clause carries information an agent needs.

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

Completeness4/5

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

For a mutation tool with six parameters, a nested extraParams object, no output schema and no annotations, the description covers purpose, key input, and mutation/versioning behavior. The remaining gaps are operational details (async behavior, model selection guidance, extraParams usage) rather than anything preventing a correct invocation.

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 coverage is 100%, so all six parameters including videoUrl and extraParams are already documented in structured fields, making 3 the baseline. The description only adds the hint that the source video defaults to the active media version, which slightly reinforces the videoUrl override semantics but adds little beyond the schema.

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 names a specific verb and resource ('Run lip sync on a video media item') and states the key input ('using a supplied audio URL'), which separates it from siblings like change_video_voice or generate_video_audio. It never explicitly names a sibling tool it is not, so it stops short of full differentiation.

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 implied rather than stated: the agent can infer it needs a video media item plus an audio URL, but there is no explicit guidance on when to pick this over change_video_voice or generate_video_audio, and no preconditions (permissions, model availability) are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.