Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

modify_shape_path

Edit shape paths in After Effects compositions by updating vertices, tangents, and closure properties to adjust vector graphics and animations.

Instructions

Modify an existing shape path

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": {
      "compId": "<compId>",
      "layerIndex": "<layerIndex>",
      "pathPropertyPath": "<pathPropertyPath>",
      "path": "<path>"
    },
    "name": "modify_shape_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
layerIndexYesIndex of the shape layer
pathPropertyPathYesProperty path to the shape path (e.g., 'Contents.Shape 1.Path 1')
pathYes
setKeyframeNoWhether to set a keyframe at current time

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool modifies an existing shape path, implying a mutation operation, but fails to mention critical details like whether changes are destructive, require specific permissions, or how errors are handled. This is inadequate for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, and output expectations, leaving significant gaps in understanding how to use the tool effectively 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?

The description adds no parameter information beyond what's already in the schema, which has 80% coverage. Since the schema descriptions are comprehensive for parameters like 'pathPropertyPath' and 'path', the baseline score of 3 is appropriate, as the description doesn't compensate for the remaining 20% gap 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 clearly states the verb ('modify') and resource ('existing shape path'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'modify_mask_path' or 'add_shape_path' that also manipulate paths, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'modify_mask_path' or 'add_shape_path', nor does it mention prerequisites such as needing an existing shape path to modify. This leaves the agent without contextual usage information.

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