Skip to main content
Glama

list_library_graphics

Lists Motion Graphics templates stored in your Creative Cloud Libraries, with an optional filter, so you can find titles and graphics to add to a Premiere Pro timeline.

Instructions

Motion Graphics templates stored in your Creative Cloud Libraries

Input Schema

NameRequiredDescriptionDefault
filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Since no annotations are provided, the description must carry the behavioral burden. It only states the resource; it doesn't clarify if this is a read-only operation, which is critical for a listing tool.

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?

The description is a single, direct sentence that explains the resource being acted upon. It is concise and contains no unnecessary filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that takes a filter input, the description is highly incomplete. It provides the target resource but gives no context about the operation, its safety profile, or how the provided filter parameter functions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 0%, and the description does not mention the 'filter' parameter at all. It adds zero semantic meaning to the input, leaving the agent to guess what filtering is possible or how to apply it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 'Motion Graphics templates stored in your Creative Cloud Libraries.' However, given the existence of 'list_mogrts' and 'import_mogrt', it doesn't provide enough specific context to distinguish this from other listing tools.

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

Usage Guidelines1/5

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

The description offers zero guidance on when or how to use this tool versus alternatives. There is no reference to other similar tools (like list_mogrts) which are present in the sibling list.

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