Skip to main content
Glama

VideoGen

by io.github.dg314
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoOptional for OPEN_SUBMIT_FEEDBACK. Prefills the ticket description (capped).
actionYesApp operation to open after sign-in, such as navigation, feedback, or integration management.
categoryNoFeedback classification for OPEN_SUBMIT_FEEDBACK. Omit or pass null to let the user choose.
providerNoRequired for OPEN_MANAGE_INTEGRATION. Integration provider key, such as GOOGLE or SLACK, identifying the connection to manage.
capabilityNoOptional for OPEN_INTEGRATIONS_PICKER. Capability filter (e.g. KNOWLEDGE_SOURCE), or null for all.
articleSlugNoRequired for OPEN_HELP_ARTICLE. Help-center search text, such as an article title or its URL slug; the link opens matching search results.
destinationNoRequired for NAVIGATE. In-app keys like PROJECTS, BILLING_SETTINGS, SUPPORT; or HELP_CENTER / API_DOCS.
suggestedLocaleNoFor 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

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute URL to open in a browser. After VideoGen sign-in, the app applies the action (modal or navigation).
actionYesThe deep-link action that was resolved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry the read-only/idempotent/non-destructive safety profile, so the bar is lower, and the description adds genuine context beyond them: the URL opens a modal or navigates only after sign-in (auth-gated), and the agent should hand the URL to the user rather than surfacing it inline. It stops short of describing expiry or format of the returned URL.

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 purpose and followed by the usage rule. The long parenthetical action list is informative but slightly heavy; otherwise there is no wasted wording.

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?

With an output schema present, the description needn't explain the return value, and all 8 parameters are schema-documented. It still supplies the one behavioral fact an agent needs (return the URL for the user to open), so it is complete for this 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%, so each parameter is already documented (action enum, provider, destination, articleSlug, etc.). The description echoes the action categories but does not add syntax or mapping detail beyond what the schema provides, so the baseline 3 applies.

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 specific verb ('Build a VideoGen app URL') and resource, plus enumerates the concrete destinations (upgrade, credits, top-ups, invite, feedback, integrations, settings, NAVIGATE). It is clearly the only URL-builder among the sibling generation/entity tools, so an agent can distinguish it immediately.

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?

Explicitly says when to prefer it ('when the user needs to complete something in the VideoGen UI that MCP tools cannot do inline — especially credits or plan gates') and gives the operative constraint that selects it. This is a real when-to-use boundary rather than an implied one.

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

All VideoGen toolsInspect
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.

Resources