Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove filmstrip

remove_filmstrip
Idempotent

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Remove a filmstrip by id (get_edl fx), or every one ('all', the default).

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

Input Schema

NameRequiredDescriptionDefault
idsNo
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. Added

TDQS

A3.5/5.0
Behavior3/5

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

Adds context beyond the annotations: that the call is scoped strictly to project_id and returns project identity with the result — valuable because the connection's navigation pointer is explicitly not used. However, it never addresses reversibility or the mass-removal risk implied by the 'all' default, which sits uneasily with destructiveHint=false; an agent reading annotations alone would not expect bulk data loss.

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 tight sentences with the scoping constraint front-loaded, and every clause carries information (scope, id source, default). Minor friction from the unexplained abbreviation 'fx' in 'get_edl fx'.

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

Completeness3/5

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

For a 2-parameter removal tool with no output schema, the description covers scope, id semantics, and default behavior. It is thin on outcomes: no statement of what happens to nonexistent ids, whether the project state change is reversible, or anything about the returned payload beyond 'project identity'.

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

Parameters4/5

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

Schema coverage is only 50% (only project_id is described in the schema), and the description compensates well: it explains that ids accepts a single id sourced from get_edl or the magic string 'all', and that 'all' is the default when ids is omitted. That is genuine meaning the schema does not carry.

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 ('Remove a filmstrip by id') plus scope ('every one, the default'), and points at get_edl as the id source. It is clearly distinguishable from its inverse sibling add_filmstrip, though it doesn't name that sibling explicitly to confirm the inverse relationship.

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?

Gives real call-time guidance: ids come from get_edl, and omitting ids removes every filmstrip. It does not state prerequisites, whether the removal is undoable, or what to do if an id is stale, so it stops short of explicit when/when-not guidance.

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