Skip to main content
Glama
Sign In
MCP Bridge for Adobe Premiere Pro

MCP Bridge for Adobe Premiere Pro

by takafumi-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_tool_schema

Retrieve the full JSON input schema for a Premiere tool name returned by search_tools, then call invoke_tool with the correct parameters.

Instructions

Return the full JSON input schema for one Premiere tool name from search_tools. After reading it, call invoke_tool.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact tool name, e.g. trim_clip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.11

TDQS

A4.2/5.0
Behavior4/5

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

There are no annotations, so the description carries the full burden of explaining behavior. It discloses that this tool only returns a schema and implies that it does not execute tools by instructing the agent to call invoke_tool afterward. It does not cover error cases, but for an introspection tool this is adequate.

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?

Two concise sentences provide the core behavior and the intended next action. There is no filler, repetition, or unnecessary detail.

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 tool with no output schema, the description explains what is returned and how to continue the workflow. It could mention behavior for an invalid or unknown tool name, but the essential information for correct invocation is present.

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 schema coverage is 100% and already documents the 'name' parameter with an example. The description adds only that the name should come from search_tools, which is helpful context but does not substantially enrich parameter understanding beyond the schema.

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 clearly states the resource: 'full JSON input schema for one Premiere tool name.' It also distinguishes the tool from siblings by tying it to search_tools and instructing that invoke_tool should come next.

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

Usage Guidelines4/5

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

The description places the tool in a workflow: tool names come from search_tools, and after reading the schema the agent should call invoke_tool. It does not explicitly say when not to use this tool, but the sequential guidance is clear and actionable.

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