VideoGen

Get app deep link

get_app_deep_link

Read-onlyIdempotent

Build a VideoGen app URL that opens a modal or navigates after the user signs in (upgrade, buy credits, enable top-ups, invite teammates, submit feedback, integrations, account settings, or a NAVIGATE destination). Prefer this when the user needs to complete something in the VideoGen UI that MCP tools cannot do inline — especially credits or plan gates. Return the url to the user so they can open it.

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": {
      "action": "<action>"
    },
    "name": "get_app_deep_link"
  }
}

Input Schema

Name	Required	Description
`text`	No	Optional for OPEN_SUBMIT_FEEDBACK. Prefills the ticket description (capped).
`action`	Yes	App operation to open after sign-in, such as navigation, feedback, or integration management.
`category`	No	Feedback classification for OPEN_SUBMIT_FEEDBACK. Omit or pass null to let the user choose.
`provider`	No	Required for OPEN_MANAGE_INTEGRATION. Integration provider key, such as GOOGLE or SLACK, identifying the connection to manage.
`capability`	No	Optional for OPEN_INTEGRATIONS_PICKER. Capability filter (e.g. KNOWLEDGE_SOURCE), or null for all.
`articleSlug`	No	Required for OPEN_HELP_ARTICLE. Help-center search text, such as an article title or its URL slug; the link opens matching search results.
`destination`	No	Required for NAVIGATE. In-app keys like PROJECTS, BILLING_SETTINGS, SUPPORT; or HELP_CENTER / API_DOCS.
`suggestedLocale`	No	For OPEN_LANGUAGE_SELECTOR, preselect a UI language using an app locale code such as en or es. Unsupported codes are ignored. The user can choose another language.

Output Schema

Name	Required	Description	Default
`url`	Yes	Absolute URL to open in a browser. After VideoGen sign-in, the app applies the action (modal or navigation).
`action`	Yes	The deep-link action that was resolved.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 4, 2026

removedInput schema / properties / capability / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / capability / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / suggestedLocale / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / suggestedLocale / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / text / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / text / type

Added value: +[
+  "string",
+  "null"
+]

Changed5 schema fields changedOct 16, 2026

changedInput schema / properties / action / description

Previous value: -"Assistant COMMON action to deep-link into the VideoGen app (opens a modal or navigates after sign-in)."New value: +"App operation to open after sign-in, such as navigation, feedback, or integration management."

changedInput schema / properties / articleSlug / description

Previous value: -"Required for OPEN_HELP_ARTICLE. Help-center article slug / search query."New value: +"Required for OPEN_HELP_ARTICLE. Help-center search text, such as an article title or its URL slug; the link opens matching search results."

changedInput schema / properties / category / description

Previous value: -"Optional for OPEN_SUBMIT_FEEDBACK. Ticket category, or null to let the user pick."New value: +"Feedback classification for OPEN_SUBMIT_FEEDBACK. Omit or pass null to let the user choose."

changedInput schema / properties / provider / description

Previous value: -"Required for OPEN_MANAGE_INTEGRATION. Integration provider id (e.g. GOOGLE, SLACK)."New value: +"Required for OPEN_MANAGE_INTEGRATION. Integration provider key, such as GOOGLE or SLACK, identifying the connection to manage."

changedInput schema / properties / suggestedLocale / description

Previous value: -"Optional for OPEN_LANGUAGE_SELECTOR. Suggested locale code (e.g. en-US)."New value: +"For OPEN_LANGUAGE_SELECTOR, preselect a UI language using an app locale code such as en or es. Unsupported codes are ignored. The user can choose another language."

First observedOct 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds the important behavioral fact the annotations cannot: the link requires the user to sign in, and the tool only returns a URL rather than performing the action, so the agent must hand it to the user.

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 sentences, front-loaded with the capability and followed by the routing rule and the hand-off instruction. The long parenthetical of destinations is dense but functional; nothing is padded or redundant.

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?

With annotations covering safety, an output schema covering the returned URL, and full parameter documentation, the description only needed to add purpose and routing, which it does. The one omission is that it doesn't clarify what happens for NAVIGATE versus modal actions beyond the parenthetical, a minor gap for an 8-parameter tool.

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% and each parameter already documents its own conditional requirement (provider for OPEN_MANAGE_INTEGRATION, destination for NAVIGATE, articleSlug for OPEN_HELP_ARTICLE), so the schema does the heavy lifting. The description's field lists restate rather than extend that, leaving the baseline 3 appropriate.

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?

"Build a VideoGen app URL that opens a modal or navigates after the user signs in" names a specific verb and resource and scopes the output. The parenthetical enumeration of destinations (upgrade, credits, top-ups, invites, feedback, integrations, settings, NAVIGATE) maps directly to the action enum, so the agent knows exactly what this produces.

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

Usage Guidelines4/5

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

"Prefer this when the user needs to complete something in the VideoGen UI that MCP tools cannot do inline — especially credits or plan gates" gives a clear selection rule against the rest of the toolset and a priority cue. It falls short of 5 only because it doesn't name specific alternatives (e.g. open_home, open_uploader) that overlap with the navigation case.

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

All VideoGen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.