Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_remove_render_queue_item

Removes a render queue item at the specified index, preventing unwanted outputs from being rendered in After Effects.

Instructions

Remove an item from the render queue by its index

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": {
      "index": "<index>"
    },
    "name": "ae_remove_render_queue_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes1-based render queue item index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly identifies the mutation and scope, but it does not mention irreversibility, behavior for an invalid index, or what happens if the item is currently rendering. Basic transparency is present, but edge-case behavior is absent.

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?

A single sentence with no filler. The verb, target, and selection mechanism are all present and front-loaded, making the tool's purpose immediately clear.

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 one-parameter removal action with no output schema, the description plus the input schema supplies the essential information needed to invoke the tool correctly. It does not describe return values, but that is a minor omission for such a simple destructive action.

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 coverage is 100%, and the parameter already has a clear description ('1-based render queue item index'). The description adds no additional parameter meaning beyond restating 'by its index', so the baseline 3 applies.

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 ('Remove'), a specific resource ('an item from the render queue'), and the selection mechanism ('by its index'). It is clearly distinct from sibling tools like ae_clear_render_queue and ae_get_render_queue.

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?

The wording 'by its index' implies the caller must first know the 1-based index, likely from ae_get_render_queue, but the description does not explicitly say when to use this tool or contrast it with alternatives such as ae_clear_render_queue for removing all items. Usage context is implied, not stated.

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