Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove ui scene

remove_ui_scene
Idempotent

Removes identified interface scenes and the footage in their owned media slots.

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": {
      "ids": "<ids>",
      "project_id": "<project_id>"
    },
    "name": "remove_ui_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly=false, destructiveHint=false, idempotent=true, so the safety profile is largely carried by structured data. The description's key addition is that the footage in owned media slots is also removed, but it leaves the critical question unanswered: are the underlying media assets deleted from the project library, or only the clips placed in the scene? That ambiguity sits awkwardly against destructiveHint=false and is exactly what an agent needs to know before calling.

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?

A single front-loaded sentence with no filler; the removal scope is stated before the side effect. It is efficient, though its brevity is achieved partly by omitting the details an agent actually needs.

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

Completeness2/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, an undocumented `ids` array, and no return/error information, the description does too little. It does not say what happens to remaining scenes, whether the operation is undoable, or what the response confirms.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%; project_id is documented in the schema (including the navigation-pointer caveat), but `ids` is a bare array of strings with no description anywhere. The description says 'identified interface scenes' but never clarifies that ids are scene identifiers, what shape they take, or where an agent obtains them.

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?

States a specific verb and resource ('Removes identified interface scenes') and adds the side effect that footage in their owned media slots goes with them. That distinguishes it from the other remove_* siblings (remove_typography_scene, remove_editorial_graphic), though it never explicitly names a sibling it is not, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus the many adjacent removal tools, and no prerequisites (does the project need to be open? must the scene be currently placed?). The only usage signal is implicit in the verb.

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

All Valmera — AI Video Editor 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