Skip to main content
Glama
AE Motion MCP
by dha-aa

Get Comp

get_comp
Read-onlyIdempotent

Retrieves composition settings and layer data, including IDs, names, kinds, timing, parenting, blend modes, and flags; supports name/kind/time filters and pagination for large comps.

Instructions

Get composition settings and its layers, top first (id, name, kind, non-default in/out/start, parent, blend mode, flags). Big comps: filter by name (substring), kind or at (seconds: layers visible then), page with limit (default 150) / offset; kinds counts all layers.

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": {
      "comp_id": "<comp_id>"
    },
    "name": "get_comp"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
kindNo
nameNo
limitNo
offsetNo
comp_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.25.0
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "text",
      -  "shape",
      -  "solid",
      -  "footage",
      -  "precomp",
      -  "null",
      -  "adjustment",
      -  "camera",
      -  "light"
      -]New value: +[
      +  "text",
      +  "shape",
      +  "solid",
      +  "footage",
      +  "precomp",
      +  "null",
      +  "adjustment",
      +  "camera",
      +  "light",
      +  "mesh"
      +]
  2. First observedv2.22.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description need not restate safety. It adds useful behavioral detail beyond annotations: layers are returned top first, non-default fields are noted, pagination defaults to 150, and "kinds counts all layers" is a subtle filtering nuance.

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 dense, front-loaded paragraph with no filler, moving from purpose to return fields to filtering/pagination. Its shorthand is compact and each clause contributes useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a getter with six parameters and no output schema, it lists the returned layer fields and explains filtering and pagination. It omits details of the composition settings themselves and the overall response envelope, but it is adequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden well: it explains name as substring, at as seconds with visibility semantics, limit default 150, offset paging, and kind filtering. comp_id is not described but is obvious as the required target; "kinds counts all layers" is slightly ambiguous.

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 states a specific verb and resource: "Get composition settings and its layers," and adds ordering plus returned layer fields. It is distinguishable from siblings like get_layer and get_project, though it does not explicitly name an alternative tool.

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

Usage Guidelines4/5

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

It gives clear usage context for big comps: filter by name substring, kind, or at, and page with limit/offset. It does not provide explicit when-not guidance or name sibling alternatives, but the filtering guidance is practical and specific.

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