Retrieve all keyframes for a clip component parameter using its clip ID, component, and parameter name, so you can inspect animation timing.
Gets all keyframes for a clip component parameter.
| Name | Required | Description | Default |
|---|---|---|---|
| clipId | Yes | The ID of the clip | |
| paramName | Yes | The display name of the parameter | |
| componentName | Yes | The display name of the component |
Changes observed during successful MCP inspections.
v1.3.0-ibintec.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Gets' implies a read-only operation, but the description does not state return shape, ordering, interpolation details, or behavior when no keyframes exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. Every word contributes to the meaning, making it an appropriately concise definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description should clarify what 'gets all keyframes' returns (e.g., list of keyframe times/values). It also does not explain the clip-component-parameter relationship or edge cases, leaving the agent under-informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and property descriptions already define clipId, componentName, and paramName. The description adds the relational context that keyframes belong to a parameter within a clip component, which is marginal value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Gets') with a clear resource ('all keyframes') and target scope ('for a clip component parameter'). This clearly distinguishes it from sibling keyframe tools like add_keyframe or remove_keyframe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 get_value_at_time, get_effect_properties, or get_keyframe_interpolation. The context is implied but no exclusions or alternative tool names are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.