Skip to main content
Glama

Get robot parameter help

transloadit_get_robot_help

Retrieve detailed summaries, parameters, and examples for any Transloadit robot to configure media processing tasks.

Instructions

Returns a robot summary and parameter details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
robot_nameNo
robot_namesNo
detail_levelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
robotNo
robotsNo
not_foundNo

Implementation Reference

  • Registers the 'transloadit_get_robot_help' tool with the MCP server, including input/output schemas and the handler closure.
    server.registerTool(
      'transloadit_get_robot_help',
      {
        title: 'Get robot parameter help',
        description: 'Returns a robot summary and parameter details.',
        inputSchema: getRobotHelpInputSchema,
        outputSchema: getRobotHelpOutputSchema,
      },
      ({ robot_name, robot_names }) => {
        const splitComma = (value: string): string[] =>
          value
            .split(',')
            .map((part) => part.trim())
            .filter(Boolean)
    
        const prefersSingle =
          typeof robot_name === 'string' && robot_name.trim() !== '' && !robot_name.includes(',')
    
        const requested =
          robot_names && robot_names.length > 0
            ? robot_names
            : robot_name
              ? splitComma(robot_name)
              : []
    
        if (requested.length === 0) {
          return buildToolError('mcp_missing_args', 'Provide robot_name or robot_names.')
        }
    
        const robots: Array<{
          name: string
          summary: string
          required_params: unknown[]
          optional_params: unknown[]
          examples?: unknown[]
        }> = []
        const notFound: string[] = []
    
        for (const name of requested) {
          if (!isKnownRobot(name)) {
            notFound.push(name)
            continue
          }
          const help = getRobotHelp({
            robotName: name,
            detailLevel: 'full',
          })
    
          robots.push({
            name: help.name,
            summary: help.summary,
            required_params: help.requiredParams,
            optional_params: help.optionalParams,
            examples: help.examples,
          })
        }
    
        if (prefersSingle) {
          return buildToolResponse({
            status: 'ok',
            robot: robots[0],
            not_found: notFound.length > 0 ? notFound : undefined,
          })
        }
    
        return buildToolResponse({
          status: 'ok',
          robots,
          not_found: notFound.length > 0 ? notFound : undefined,
        })
      },
    )
  • Handler function that accepts robot_name/robot_names, looks up robot help via getRobotHelp(), and returns results (single or multiple robots) with not_found reporting.
    ({ robot_name, robot_names }) => {
      const splitComma = (value: string): string[] =>
        value
          .split(',')
          .map((part) => part.trim())
          .filter(Boolean)
    
      const prefersSingle =
        typeof robot_name === 'string' && robot_name.trim() !== '' && !robot_name.includes(',')
    
      const requested =
        robot_names && robot_names.length > 0
          ? robot_names
          : robot_name
            ? splitComma(robot_name)
            : []
    
      if (requested.length === 0) {
        return buildToolError('mcp_missing_args', 'Provide robot_name or robot_names.')
      }
    
      const robots: Array<{
        name: string
        summary: string
        required_params: unknown[]
        optional_params: unknown[]
        examples?: unknown[]
      }> = []
      const notFound: string[] = []
    
      for (const name of requested) {
        if (!isKnownRobot(name)) {
          notFound.push(name)
          continue
        }
        const help = getRobotHelp({
          robotName: name,
          detailLevel: 'full',
        })
    
        robots.push({
          name: help.name,
          summary: help.summary,
          required_params: help.requiredParams,
          optional_params: help.optionalParams,
          examples: help.examples,
        })
      }
    
      if (prefersSingle) {
        return buildToolResponse({
          status: 'ok',
          robot: robots[0],
          not_found: notFound.length > 0 ? notFound : undefined,
        })
      }
    
      return buildToolResponse({
        status: 'ok',
        robots,
        not_found: notFound.length > 0 ? notFound : undefined,
      })
    },
  • Zod input schema for get_robot_help: optional robot_name (string), robot_names (array of strings), and backward-compat detail_level.
    const getRobotHelpInputSchema = z.object({
      robot_name: z.string().optional(),
      robot_names: z.array(z.string()).optional(),
      // Backward compatible input; ignored on purpose (we always return full docs).
      detail_level: z.enum(['summary', 'params', 'examples']).optional(),
    })
  • Zod output schema for get_robot_help: status, optional single robot, optional robots array, and optional not_found array.
    const getRobotHelpOutputSchema = z
      .object({
        status: z.enum(['ok', 'error']),
        // For backward compatibility, we still return `robot` for single-robot requests via `robot_name`.
        robot: robotHelpOutputSchema.optional(),
        robots: z.array(robotHelpOutputSchema).optional(),
        not_found: z.array(z.string()).optional(),
      })
      .refine((value) => value.status !== 'ok' || value.robot || value.robots, {
        message: 'Expected robot or robots for ok status.',
      })
  • Core helper function getRobotHelp() that resolves robot meta and schema to build a RobotHelp object with name, summary, params, and examples.
    export const getRobotHelp = (options: RobotHelpOptions): RobotHelp => {
      const detailLevel = options.detailLevel ?? 'summary'
      const { byPath, byName } = getMetaIndex()
      const schemaIndex = getSchemaIndex()
    
      const path = resolveRobotPath(options.robotName)
      const meta = byPath.get(path) ?? byName.get(options.robotName) ?? null
      const summary = meta ? selectSummary(meta) : `Robot ${path}`
      const schema = schemaIndex.get(path)
      const params = schema ? getRobotParams(schema) : { required: [], optional: [] }
    
      const help: RobotHelp = {
        name: path,
        summary,
        requiredParams: detailLevel === 'params' || detailLevel === 'full' ? params.required : [],
        optionalParams: detailLevel === 'params' || detailLevel === 'full' ? params.optional : [],
      }
    
      if ((detailLevel === 'examples' || detailLevel === 'full') && meta?.example_code) {
        const snippet = isRecord(meta.example_code) ? meta.example_code : {}
        help.examples = [
          {
            description: meta.example_code_description ?? 'Example',
            snippet,
          },
        ]
      }
    
      return help
    }
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. It only states the output nature without disclosing side effects, authentication requirements, or rate limits. For a read-oriented tool, this is acceptable but minimal.

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 concise sentence with no unnecessary words. However, it could benefit from additional context without sacrificing conciseness.

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

Completeness2/5

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

Given the tool has 3 optional parameters and an output schema, the description is too minimal. It does not explain how parameters affect behavior (e.g., difference between `robot_name` and `robot_names`, effect of `detail_level` values). The agent may misinterpret the tool's capabilities.

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 input schema has 0% description coverage, and the description does not explain the purpose or usage of any of the three parameters (`robot_name`, `robot_names`, `detail_level`). The agent has no guidance on how to fill them.

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 returns a robot summary and parameter details, which distinguishes it from sibling `transloadit_list_robots` that likely only lists robots. However, it could be more specific about what 'robot summary' includes.

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?

There is no guidance on when to use this tool versus alternatives like `transloadit_list_robots` or other sibling tools. The description does not mention 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