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

Find Effects

find_effects
Read-onlyIdempotent

Search installed effects in Adobe After Effects by display name, match name, or category, using limit/offset pagination to browse larger result sets.

Instructions

Search installed effects by display name, match name or category. Page: limit (50) / offset; matched and next_offset when there are more.

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": {
      "query": "<query>"
    },
    "name": "find_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.26.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "type": "integer"
      +}
  2. First observedv2.22.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, non-destructive read, so the description only needs to add what they cannot. It does that by disclosing the paging model: default limit of 50, offset for continuation, and that matched and next_offset appear when more results remain. Missing is any note on result ordering or match semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and followed by the paging contract, with no filler. The second sentence is telegraphic ("Page: limit (50) / offset") and slightly cryptic, but still parses quickly.

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?

With no output schema, the description usefully names the return fields matched and next_offset, and covers pagination for a simple three-parameter read tool. The remaining gap is characterizing what matched contains and how the query is matched.

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?

Schema description coverage is 0%, so the description carries the full burden on three parameters. It addresses all three: query searches display name, match name or category; limit defaults to 50; offset pages. However it never explains matching behavior for query (substring versus exact, case sensitivity, whether the three fields are ORed), which is the parameter most likely to be misused.

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?

Specific verb and resource: "Search installed effects by display name, match name or category." It scopes the search space to installed effects, which helps distinguish it from manipulation siblings such as apply_effect or edit_effect. It does not explicitly name an alternative tool, so it falls short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers this is the lookup step before apply_effect or edit_effect, but the description never says so. There is no statement of when not to use it and no named alternative such as find_fonts for the analogous font lookup.

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