Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove editorial graphic

remove_editorial_graphic
Idempotent

Removes an identified editorial composition and its owned caption suppression.

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

Input Schema

NameRequiredDescriptionDefault
idYes
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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is supplied. The description adds genuine context beyond them: removal also takes out the composition's 'owned caption suppression', a cascade an agent would not otherwise predict. It stops short of saying whether the change is undoable or what happens to non-owned caption settings.

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?

One front-loaded sentence with no filler, and the cascade side effect is attached to the main clause. The only cost is that brevity leaves the graphic-vs-composition terminology inconsistent with the tool name.

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 two-parameter mutation tool with annotations and no output schema, the description covers the core action and its side effect but omits error behaviour (unknown id, wrong project), whether the removal is reversible, and what is returned. Adequate but with clear gaps.

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 50%: project_id is well documented in the schema, and the description's 'identified editorial composition' loosely ties 'id' to the target, but neither source explains the id's format or where to obtain it. Baseline 3 applies since the schema carries half the burden.

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 ('Removes') and resource ('editorial composition') plus a cascade effect, so the operation is clear. It does not differentiate itself from the many neighbouring remove_* tools (remove_motion_graphic, remove_vector_graphic, remove_typography_scene, remove_ui_scene), and it uses 'editorial composition' where the name and sibling use 'editorial graphic'.

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?

No when-to-use guidance, no prerequisites (e.g. does the graphic need to exist first), and no mention of alternatives such as masking/hiding instead of removing. The agent must infer everything from the name and the sibling list.

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