Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Mogrt Component

get_mogrt_component
Read-onlyIdempotent

Retrieve Motion Graphics Template (MOGRT) component parameters from a timeline clip by providing its node ID. Access editable properties to adjust or inspect motion graphics settings.

Instructions

Get MOGRT (Motion Graphics Template) component parameters from a clip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the MOGRT clip on the timeline

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds the scope 'from a clip' and expands the MOGRT acronym, but does not disclose return format, error behavior, or other runtime traits. Given the rich annotations, the description does enough to earn a mid score without contradicting them.

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 a single, well-front-loaded sentence with no filler. It states the action, the resource, and the source clip efficiently, and the acronym expansion is useful rather than redundant.

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 low-complexity, read-only getter with a single fully documented parameter and an output schema, the description is nearly complete. It lacks usage guidance and return-value details, but those are largely covered by the schema, output schema, and annotations, so the provided text is sufficient for the tool's simplicity.

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?

The input schema fully documents the single parameter node_id with a clear description, so schema coverage is 100%. The tool description adds no additional parameter syntax, defaults, or constraints, so the baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Get' and the specific resource 'MOGRT component parameters from a clip', and helpfully expands the acronym MOGRT. It does not explicitly call out sibling tools for differentiation, but the resource is specific enough that an agent can generally distinguish it from related getters like get_clip_properties or get_effect_properties.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus similar tools. The description only says what it does ('Get MOGRT component parameters from a clip') but gives no scenarios, exclusions, or pointers to alternatives. This is a clear gap given the large number of getter siblings.

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