Skip to main content
Glama

ai_modeling_motion_rename

Rename a generated motion asset by supplying its asset ID and a new title of up to 100 characters. Use it to give animated clips clear, recognizable names in Tripo Studio.

Instructions

Rename a generated motion asset.

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": {
      "asset_id": "<asset_id>",
      "title": "<title>"
    },
    "name": "ai_modeling_motion_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
asset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds almost no behavioral context beyond the operation itself: it does not mention permissions, whether existing references update, title collision behavior, or what is returned.

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?

The single sentence is front-loaded with the verb and resource and contains no wasted wording. Its brevity is appropriate in form, though the content is under-specified for the operation.

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 two required parameters, no output schema, and no parameter descriptions, this definition is too thin. It should explain return behavior, permission or auth needs, and the effect of renaming on downstream references or existing assets.

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 0%, and the description provides no explanation of asset_id or title. The parameter names and schema constraints are somewhat self-explanatory, but the description does not compensate for the missing semantic detail such as asset ID format or title uniqueness expectations.

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 (Rename) and resource (a generated motion asset), which distinguishes it from sibling renames such as ai_modeling_canvas_rename and ai_modeling_project_rename. It is clear what operation is performed, though it does not elaborate on scope or effects.

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 alternatives named, and no prerequisites described. The agent must infer from the name that this applies to motion assets rather than canvases or projects.

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

Deploy Server

Other Tools