Skip to main content
Glama
Sign In
3D-MCP

3D-MCP

by team-plask
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

deleteClips

Remove multiple clips from 3D creative projects by specifying their identifiers using the 3D-MCP server's standardized API.

Instructions

Delete multiple Clips

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>"
    },
    "name": "deleteClips"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesClip identifiers to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden. It states 'Delete multiple Clips' but doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, permission requirements, rate limits, error handling for invalid IDs, or confirmation prompts. For a destructive operation with zero annotation coverage, this is a severe gap.

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?

The description is a single, efficient sentence with zero waste: 'Delete multiple Clips'. It is front-loaded and appropriately sized, conveying the core action without unnecessary elaboration.

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?

Given the tool's complexity (destructive batch operation), lack of annotations, and no output schema, the description is incomplete. It fails to address safety, consequences, or response format, leaving significant gaps for an AI agent to understand and invoke it correctly in context.

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 100%, with the parameter 'ids' documented as 'Clip identifiers to delete'. The description adds no additional parameter semantics beyond this, such as format examples or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract 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 'Delete multiple Clips' clearly states the action (delete) and resource (Clips), with 'multiple' indicating batch operation. It distinguishes from single-item deletions like deleteBlendShapes or deleteMaterials by specifying multiple items, though not explicitly from other batch tools like batchSetProperty. The purpose is specific but could better differentiate from siblings.

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 guidance on when to use this tool versus alternatives is provided. It doesn't mention prerequisites (e.g., needing clip IDs from getClips or listClips), error conditions, or comparisons to other deletion tools like deleteMaterials. The description assumes context without explicit usage instructions.

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

Related Tools