Skip to main content
Glama

List Transloadit robots

transloadit_list_robots

Retrieve a filtered list of Transloadit's 86+ cloud robots for media processing tasks like video encoding, image manipulation, and document conversion.

Instructions

Returns a filtered list of robots with short summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo
searchNo
limitNo
cursorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
robotsYes
statusYes
next_cursorNo

Implementation Reference

  • The tool 'transloadit_list_robots' is registered and implemented in server.ts using the 'listRobots' utility from '@transloadit/node'.
      'transloadit_list_robots',
      {
        title: 'List Transloadit robots',
        description: 'Returns a filtered list of robots with short summaries.',
        inputSchema: listRobotsInputSchema,
        outputSchema: listRobotsOutputSchema,
      },
      ({ category, search, limit, cursor }) => {
        const result = listRobots({ category, search, limit, cursor })
    
        return buildToolResponse({
          status: 'ok',
          robots: result.robots,
          next_cursor: result.nextCursor,
        })
      },
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a filtered list with short summaries, but does not cover critical aspects like whether it's read-only, pagination behavior (implied by 'cursor' parameter), rate limits, authentication needs, or error handling. This leaves significant gaps for a tool with four parameters.

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 a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's core function without unnecessary elaboration.

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 (4 parameters, no annotations, but with an output schema), the description is incomplete. It lacks behavioral context and parameter explanations, though the output schema may mitigate some gaps by defining return values. However, for a list operation with filtering and pagination, more guidance is needed.

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 'filtered list' but does not explain what 'robots' are, what 'category' or 'search' filter by, how 'limit' and 'cursor' work for pagination, or the meaning of 'short summaries.' The description adds minimal semantic value beyond the bare schema.

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 tool's purpose: 'Returns a filtered list of robots with short summaries.' It specifies the verb ('Returns'), resource ('robots'), and scope ('filtered list'), though it does not explicitly differentiate from sibling tools like 'transloadit_list_templates' or 'transloadit_get_robot_help'.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'filtered list' but does not specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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