Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_clear_render_queue

Remove all pending jobs from the After Effects render queue while preserving the item currently rendering, freeing up resources for upcoming tasks.

Instructions

Remove all items from the render queue (skips items currently rendering)

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_clear_render_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it does: 'skips items currently rendering' is a non-obvious behavioral nuance beyond the destructive main action. It does not detail return values or confirm whether skipped items remain queued, but the main safety-relevant 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?

A single sentence conveys the action and the key exception with no filler. The main verb and object are front-loaded, and the parenthetical is tightly scoped to the one behavioral caveat.

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?

For a zero-parameter, no-output-schema tool, the description is complete: it identifies the target, the scope, and the one edge case (currently rendering items). Nothing else is needed for an agent to invoke it 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?

The tool takes zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies because the schema already fully covers the parameter surface.

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) and resource (render queue) with the explicit scope 'all items', clearly distinguishing it from sibling ae_remove_render_queue_item which handles single items. The parenthetical adds a meaningful boundary to the operation.

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 description implies use whenever the entire queue needs clearing, and the sibling list provides an alternative for single-item removal. However, it does not explicitly state when to choose this tool over ae_remove_render_queue_item or note any preconditions such as stopping renders first.

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