Skip to main content
Glama
Sign In
3D-MCP

3D-MCP

by team-plask
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

listClips

Retrieve and organize clips within 3D creative workflows using optional filters, pagination, and parent ID parameters to streamline content management and access.

Instructions

List all Clips

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listClips"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoOptional filters to apply
limitNoMaximum number of results
offsetNoStarting offset for pagination
parentIdNoOptional parent ID to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action without mentioning pagination behavior, rate limits, permissions, or output format, failing to add meaningful context beyond the basic operation.

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 extremely concise with a single three-word phrase, front-loaded and free of unnecessary words. It efficiently communicates the core action without waste, though this brevity contributes to gaps in other dimensions.

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 no annotations and no output schema, the description is incomplete for a tool with 4 parameters and complex filtering capabilities. It lacks details on behavior, output, and usage context, making it inadequate for effective tool invocation.

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%, so parameters are documented in the schema. The description adds no semantic details beyond implying a list operation, aligning with the baseline score when the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all Clips' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'List' and resource 'Clips' but lacks detail on scope or differentiation from sibling tools like 'getClips', leaving the purpose vague beyond basic listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'getClips' or other list tools. The description offers no context, prerequisites, or exclusions, leaving the agent without usage direction.

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