Viral Manager

confirm_asset_upload

Idempotent

Second step of a presigned upload_asset: once the file has been PUT to upload_url, creates the asset in the library with its name, notes, category and tags. Analysis: edits are never used for asset matching, so they are not AI-analyzed: they only get a thumbnail and their duration (analysis=skipped_not_in_matching). Raw footage (kind='rush') is always analyzed. If you rendered the file on the user's computer, delete it once this call succeeds.

Input Schema

Name	Required	Description	Default
`kind`	No	'edit' (default) = a finished reel/edit to be posted. 'rush' = raw footage meant for asset matching (e.g. migrating a library): always fully AI-analyzed.	edit
`name`	No	Asset name. Empty = the file name without its extension.
`tags`	No	Custom tags
`notes`	No	Internal notes saved on the asset (e.g. the caption or brief that came with the file)
`category`	No	Category (id or name). Empty = none.
`upload_id`	Yes	upload_id returned by upload_asset

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / kind

Added value: +{
+  "default": "edit",
+  "description": "'edit' (default) = a finished reel/edit to be posted. 'rush' = raw footage meant for asset matching (e.g. migrating a library): always fully AI-analyzed.",
+  "enum": [
+    "edit",
+    "rush"
+  ],
+  "type": "string"
+}

AddedOct 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: edits are never AI-analyzed and only get a thumbnail plus duration, while rushes are always analyzed, and it tells the agent to delete the local file after success.

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?

Front-loads the core action and sequencing, then adds the analysis caveat and cleanup note. Dense but every sentence carries information; the analysis aside is slightly verbose but relevant to choosing kind.

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 no output schema, the description covers preconditions, side effects, and post-call cleanup well. It does not say what the call returns (e.g. the created asset id), which is the main remaining gap for an agent chaining calls.

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 every parameter is already documented, including the kind enum and its analysis consequences. The description restates the name/notes/category/tags fields and the rush analysis behavior without adding format or syntax detail beyond the schema, so 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 and resource ('creates the asset in the library') and explicitly positions itself as the second step of a presigned upload_asset flow, which cleanly separates it from the sibling upload_asset. An agent can tell exactly what this does without opening the schema.

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?

Gives a clear precondition ('once the file has been PUT to upload_url') and a post-call cleanup instruction for locally rendered files. It does not explicitly name upload_asset as the prerequisite tool by name, but the sequencing is unambiguous.

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

All Viral Manager 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.

Resources

Need Help?