Skip to main content
Glama

List templates

transloadit_list_templates

Retrieve and manage Assembly Templates for media processing workflows, including built-in and custom templates with filtering options.

Instructions

List Assembly Templates (owned and/or builtin). Tip: pass include_builtin: "exclusively-latest" to list builtins only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo
sortNo
orderNo
keywordsNo
include_builtinNo
include_contentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
totalNo
errorsNo
statusYes
warningsNo
page_sizeNo
templatesYes

Implementation Reference

  • Handler function for the transloadit_list_templates tool, which uses the Transloadit API client to list templates.
    async ({ page, page_size, sort, order, keywords, include_builtin, include_content }, extra) => {
      const liveClient = createLiveClient(options, extra)
      if ('error' in liveClient) {
        return buildToolResponse({
          status: 'error',
          templates: [],
          errors: [
            {
              code: 'mcp_missing_auth',
              message:
                'Missing TRANSLOADIT_KEY/TRANSLOADIT_SECRET or Authorization: Bearer token for live API calls.',
            },
          ],
        })
      }
    
      try {
        const response = await liveClient.client.listTemplates({
          page,
          pagesize: page_size,
          sort,
          order,
          keywords,
          include_builtin,
        })
    
        const parsed = listTemplatesResponseSchema.safeParse(response)
        if (!parsed.success) {
          throw new Error('Unexpected listTemplates response shape.')
        }
    
        const items = parsed.data.items ?? []
        const includeContent = include_content ?? false
        const templates = await Promise.all(
          items.map(async (item) => {
            const base = mapTemplateListItem(item)
            if (!includeContent) return base
            const steps = await loadTemplateSteps(liveClient.client, item)
            return steps ? { ...base, steps } : base
          }),
        )
    
        return buildToolResponse({
          status: 'ok',
          templates,
          page,
          page_size: page_size,
          total: parsed.data.count ?? items.length,
        })
      } catch (error) {
        const message = error instanceof Error ? error.message : 'Failed to list templates.'
  • Registration of the transloadit_list_templates tool in the server using registerTool.
    server.registerTool(
      'transloadit_list_templates',
      {
        title: 'List templates',
        description:
          'List Assembly Templates (owned and/or builtin). Tip: pass include_builtin: "exclusively-latest" to list builtins only.',
        inputSchema: listTemplatesInputSchema,
        outputSchema: listTemplatesOutputSchema,
      },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions a filtering tip but lacks critical behavioral details such as pagination behavior, rate limits, authentication requirements, or what the output includes. The description is minimal and doesn't adequately disclose operational traits beyond the basic listing function.

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 extremely concise with two sentences, front-loaded with the main purpose and followed by a practical tip. There is no wasted verbiage, making it efficient and easy to parse.

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

Completeness3/5

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

Given the complexity of 7 parameters with no schema descriptions and an output schema present, the description is incomplete. It doesn't explain parameter effects or output structure, relying on the output schema for return values. However, the presence of an output schema mitigates some gaps, making it minimally adequate but with clear informational deficits.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all 7 parameters. It only mentions 'include_builtin' with a tip, ignoring other parameters like 'page', 'sort', 'keywords', etc. This adds minimal semantic value beyond the schema, failing to explain what parameters do or how they affect the listing.

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 'List' and the resource 'Assembly Templates', specifying both 'owned and/or builtin' templates. It distinguishes the scope but doesn't explicitly differentiate from sibling tools like 'transloadit_list_robots', which is a similar listing operation for a different resource.

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 provides a tip for listing builtins only, implying usage context for filtering builtin templates. However, it doesn't offer explicit guidance on when to use this tool versus alternatives like 'transloadit_create_assembly' or other siblings, leaving the agent to infer based on the 'list' action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/transloadit/node-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server