Skip to main content
Glama

Get Assembly status

transloadit_get_assembly_status

Check the current status of a Transloadit media processing assembly using its URL or ID to monitor encoding, conversion, or transcription progress.

Instructions

Fetch the latest Assembly status by URL or ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assembly_urlNo
assembly_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsNo
statusYes
assemblyNo
warningsNo

Implementation Reference

  • The handler implementation for the `transloadit_get_assembly_status` tool.
    async ({ assembly_url, assembly_id }, extra) => {
      const access = resolveAssemblyAccess(options, extra, { assembly_url, assembly_id })
      if ('error' in access) return access.error
    
      const assembly = await access.client.getAssembly(access.assemblyId)
    
      return buildToolResponse({
        status: 'ok',
        assembly,
      })
    },
  • Registration of the `transloadit_get_assembly_status` tool.
    server.registerTool(
      'transloadit_get_assembly_status',
      {
        title: 'Get Assembly status',
        description: 'Fetch the latest Assembly status by URL or ID.',
        inputSchema: getAssemblyStatusInputSchema,
        outputSchema: getAssemblyStatusOutputSchema,
      },
  • Input and output schema definitions for `transloadit_get_assembly_status`.
    const getAssemblyStatusInputSchema = z.object({
      assembly_url: z.string().optional(),
      assembly_id: z.string().optional(),
    })
    
    const getAssemblyStatusOutputSchema = z.object({
      status: z.enum(['ok', 'error']),
      assembly: z.unknown().optional(),
      errors: z.array(toolMessageSchema).optional(),
      warnings: z.array(toolMessageSchema).optional(),
    })
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 states the tool fetches status, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'latest' means in terms of freshness. The description is minimal and misses key operational details.

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 a single sentence that front-loads the core purpose. Every word earns its place, with no wasted text, making it easy to scan and understand quickly.

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 tool's moderate complexity (2 parameters, no annotations) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks details on usage context, parameter specifics, and behavioral transparency, making it incomplete for effective agent use without additional inference.

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. It mentions parameters ('URL or ID') but doesn't add meaning beyond the schema's property names. No details on format, constraints, or whether both parameters are required or mutually exclusive are provided, leaving gaps in understanding.

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 action ('Fetch') and resource ('Assembly status'), specifying it retrieves the latest status using either URL or ID. It distinguishes from siblings like 'transloadit_create_assembly' (creation) and 'transloadit_wait_for_assembly' (waiting), but could be more explicit about what an 'Assembly' is in this context.

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 alternatives. It doesn't mention prerequisites, such as needing an existing assembly, or compare it to siblings like 'transloadit_wait_for_assembly' for monitoring completion. The description implies usage by stating what it does but lacks explicit context or exclusions.

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