Valmera — AI Video Editor

List motion templates

list_motion_templates

Read-only

Lists available motion-graphics templates with their purposes, parameters and optional sound cues.

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": "list_motion_templates"
  }
}

Input Schema

Name	Required	Description
`category`	No	Optional filter: type, data, callout, social, layout, transition, texture, cta, caption.
`template`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- addedInput schema / properties / template
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedNov 6, 2026

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."

AddedOct 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing what each listed item contains (purpose, parameters, optional sound cues), which matters because there is no output schema. It says nothing about pagination, ordering, or whether results are project-scoped, which leaves gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the payload description is packed into the same clause rather than a separate paragraph. Nothing is redundant.

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 simple three-parameter read tool with no output schema this is close to adequate, but it omits the fact that results are scoped to a required project_id and says nothing about using the category/template filters. An agent still needs the schema to understand how to narrow the listing.

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 description coverage is 67%, so the schema already explains category values and the project_id navigation-pointer caveat. The word "parameters" in the description refers to template parameters, not the tool's own arguments, so it adds essentially no meaning beyond the schema; the undocumented 'template' parameter is not clarified either.

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?

The description gives a specific verb and resource ("Lists available motion-graphics templates") plus the payload contents (purposes, parameters, sound cues), so an agent knows exactly what it retrieves. It does not distinguish itself from adjacent listing tools such as list_assets or list_music_library, so it falls 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 explicit when-to-use guidance, no statement that this is the discovery step preceding add_motion_graphic or set_motion_graphic, and no mention of prerequisites such as the required project_id. The agent must infer the workflow entirely from the tool name.

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 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.