Skip to main content
Glama
ConformLabs

surehand-mcp

Official
by ConformLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find properties

ae_find_properties
Read-onlyIdempotent

Find properties by name or match name across every layer of a composition, returning ready-to-use paths with values, expressions, and errors; filter to animated or expression properties.

Instructions

Search every layer of a comp (or one layer) for properties whose name or match name contains the query, e.g. "opacity", "blur", "Source Text", "ADBE Fill Color". Returns ready-to-use paths with values (and expressions with their errors). Filter to animated or expression properties. Needs a query or a filter; stops at limit and sets truncated. Read-only. Use it when you know a property's name but not its layer or path; to browse one layer's tree use ae_get_properties.

Input Schema

NameRequiredDescriptionDefault
compNoComposition: item id (number) or exact name. Omit (or "active") for the active/open composition.
layerNoOnly search this layer: 1-based index or exact name (default: every layer).
limitNoMax results, 1-1000 (default 100).
queryNoCase-insensitive text to match in the property name or match name. Omit to list all matches of the filters.
onlyAnimatedNoOnly properties with keyframes.
onlyExpressionsNoOnly properties with an expression.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • changedInput schema / properties / layer / description
      Previous value: -"Layer: 1-based index (number) or exact layer name."New value: +"Only search this layer: 1-based index or exact name (default: every layer)."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 100."New value: +"Max results, 1-1000 (default 100)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, and the description reinforces this. Beyond annotations, it adds useful behavior: returned paths include values and expression errors, limit truncation sets 'truncated', and the tool requires a query or filter. It does not cover permissions or output structure in exhaustive detail, so a 4 is appropriate.

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 dense and front-loaded: use case, scope, examples, return behavior, filters, constraints, and the sibling alternative are all stated without repetition. Every sentence adds actionable information for an agent.

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

Completeness5/5

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

There is no output schema, but the description compensates by explaining that results include ready-to-use paths, values, expression errors, and truncation state. With six fully described parameters and clear usage guidance, an agent has enough information to invoke the tool correctly.

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 schema already documents each parameter well. The description adds meaningful framing about what query matches, what the animated/expression filters do, and that limit truncation is signaled, which goes beyond the individual schema fields.

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?

The description uses a specific verb and resource ('Search every layer of a comp... for properties') and clearly states what the tool returns. It also distinguishes this tool from the sibling browse tool by naming ae_get_properties as the alternative for browsing a layer's tree.

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?

It explicitly states when to use this tool — 'when you know a property's name but not its layer or path' — and names the alternative for browsing a single layer's tree. It also states the prerequisite that a query or filter is required, preventing misuse.

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