Skip to main content
Glama
Sign In
surehand-mcp

surehand-mcp

Official
by ConformLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get composition info

ae_get_comp_info
Read-onlyIdempotent

Retrieve an After Effects composition's settings, markers, and paged layer summary to see what a comp contains. Use it before inspecting single layers or mapping nested precomps.

Instructions

Composition settings and markers plus a summary of its layers (index, id, name, type, timing, parent, switches). Large comps are paged: use layerOffset/layerLimit (see totalLayers / nextLayerOffset in the result). Read-only. Use it to see what a comp contains; for one layer in full use ae_get_layer_info, for nested precomps, parenting and expression links ae_get_comp_map.

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": "ae_get_comp_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
compNoComposition: item id (number) or exact name. Omit (or "active") for the active/open composition.
layerLimitNoMax layers to return (default 150).
layerOffsetNoSkip this many layers (default 0).
includeLayersNoInclude the layer summary (default true); false returns only the comp's settings and markers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / includeLayers / description
      Previous value: -"Default true."New value: +"Include the layer summary (default true); false returns only the comp's settings and markers."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so "Read-only" is largely redundant, but the description adds genuinely new behavior: large comps are paged and the response carries totalLayers and nextLayerOffset. It does not explain what markers or switches contain, but the core operational behavior is disclosed.

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?

Three sentences, front-loaded with what is returned, then paging, then disambiguation. The parenthetical field list is dense but informative, and no sentence is filler.

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?

There is no output schema, so the description has to describe returns, and it does so at the field-name level plus pagination guidance. It stops short of explaining the shape of settings/markers or default page size interplay, which leaves a minor gap for a zero-required-param read tool.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by tying layerOffset/layerLimit to the paged result fields rather than restating them. includeLayers is only implied through "summary of its layers," which is why this is not a 5.

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

Purpose5/5

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

States a specific verb and resource (get comp info) and enumerates exactly what comes back: settings, markers, and a layer summary with index, id, name, type, timing, parent, switches. It is clearly differentiable from ae_get_layer_info and ae_get_comp_map, which are named for their narrower scopes.

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

Usage Guidelines5/5

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

Gives explicit routing: use this to see what a comp contains, ae_get_layer_info for one layer in full, ae_get_comp_map for nested precomps, parenting and expression links. It also states when to page and which result fields drive pagination (totalLayers / nextLayerOffset).

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