Skip to main content
Glama

Get canonical action schema

get_action_schema
Read-only

Retrieve full JSON input schemas, parameter constraints, and descriptions for canonical editor actions and read tools to validate and call them correctly.

Instructions

Fetch the full JSON inputSchema, parameter constraints, and description for any canonical editor action (e.g. COLOR_GRADE, TRIM_LAYER, GENERATE_CAPTIONS, PLAN_MOTION_GRAPHICS, RENDER_PREVIEW, EXPORT_VIDEO) or read tool (e.g. list_layers, query_transcript, inspect_layer).

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

Input Schema

NameRequiredDescriptionDefault
actionYesCanonical action name or read tool name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations establish the safety profile, and "Fetch" is consistent with them. The description usefully adds the returned content and breadth of supported action types, especially since no output schema is supplied, but it does not explain behavior for unknown names or other failures.

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?

A single front-loaded sentence efficiently conveys the operation, returned content, and scope. The nine examples are concrete but more than necessary, making the sentence somewhat list-heavy.

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 simple one-parameter, read-only introspection tool, the description covers the accepted input categories and expected returned content well enough to support invocation. Its main remaining gaps are valid-name discovery, invalid-name behavior, and an explicit place in the action-execution workflow.

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 sole action parameter is already fully described in the schema, establishing a baseline of 3. The description adds concrete uppercase action identifiers and lowercase read-tool identifiers, making valid inputs more tangible, although it does not clarify case sensitivity or how to discover the complete set of valid names.

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 uses a specific verb, "Fetch," and identifies both the resource and returned contents: the full JSON inputSchema, parameter constraints, and description for canonical editor actions or read tools. It is clear that this retrieves metadata rather than performing an edit, but it does not explicitly differentiate itself from execution-oriented siblings such as execute_action.

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?

Needing an action's inputSchema or constraints implies an introspection step before constructing a call, but that workflow is never stated. There is no explicit when-to-use guidance, exclusion, or direction to use the result with execute_action or execute_batch.

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