Skip to main content
Glama
folderr-tech

Folderr

Official
by folderr-tech

execute_workflow

Run automated workflows in Folderr by providing workflow ID and required inputs to trigger predefined processes.

Instructions

Execute a workflow with the required inputs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesID of the workflow
inputsYesInput values required by the workflow

Implementation Reference

  • The handler function that checks authentication, makes a POST request to /api/workflows/api-client/{workflow_id} with inputs, and returns the response or error.
    private async handleExecuteWorkflow(args: any) {
      if (!this.config.token) {
        throw new McpError(ErrorCode.InvalidRequest, 'Not logged in');
      }
    
      try {
        const response = await this.axiosInstance.post(
          `/api/workflows/api-client/${args.workflow_id}`,
          args.inputs
        );
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to execute workflow: ${error.response?.data?.message || error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema for the execute_workflow tool, defining workflow_id and inputs as required parameters.
    {
      name: 'execute_workflow',
      description: 'Execute a workflow with the required inputs',
      inputSchema: {
        type: 'object',
        properties: {
          workflow_id: {
            type: 'string',
            description: 'ID of the workflow',
          },
          inputs: {
            type: 'object',
            description: 'Input values required by the workflow',
            additionalProperties: true,
          },
        },
        required: ['workflow_id', 'inputs'],
      },
    },
  • src/index.ts:229-230 (registration)
    The switch case in CallToolRequestSchema handler that dispatches execute_workflow calls to the handleExecuteWorkflow method.
    case 'execute_workflow':
      return await this.handleExecuteWorkflow(request.params.arguments);
  • src/index.ts:109-213 (registration)
    The ListToolsRequestSchema handler that registers the execute_workflow tool by including it in the tools list.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'set_api_token',
          description: 'Set an API token for authentication (alternative to login)',
          inputSchema: {
            type: 'object',
            properties: {
              token: {
                type: 'string',
                description: 'API token generated from Folderr developers section',
              },
            },
            required: ['token'],
          },
        },
        {
          name: 'login',
          description: 'Login to Folderr with email and password',
          inputSchema: {
            type: 'object',
            properties: {
              email: {
                type: 'string',
                description: 'User email',
              },
              password: {
                type: 'string',
                description: 'User password',
              },
            },
            required: ['email', 'password'],
          },
        },
        {
          name: 'list_assistants',
          description: 'List all available assistants',
          inputSchema: {
            type: 'object',
            properties: {},
            required: [],
          },
        },
        {
          name: 'ask_assistant',
          description: 'Ask a question to a specific assistant',
          inputSchema: {
            type: 'object',
            properties: {
              assistant_id: {
                type: 'string',
                description: 'ID of the assistant to ask',
              },
              question: {
                type: 'string',
                description: 'Question to ask the assistant',
              },
            },
            required: ['assistant_id', 'question'],
          },
        },
        {
          name: 'list_workflows',
          description: 'List all available workflows',
          inputSchema: {
            type: 'object',
            properties: {},
            required: [],
          },
        },
        {
          name: 'get_workflow_inputs',
          description: 'Get the required inputs for a workflow',
          inputSchema: {
            type: 'object',
            properties: {
              workflow_id: {
                type: 'string',
                description: 'ID of the workflow',
              },
            },
            required: ['workflow_id'],
          },
        },
        {
          name: 'execute_workflow',
          description: 'Execute a workflow with the required inputs',
          inputSchema: {
            type: 'object',
            properties: {
              workflow_id: {
                type: 'string',
                description: 'ID of the workflow',
              },
              inputs: {
                type: 'object',
                description: 'Input values required by the workflow',
                additionalProperties: true,
              },
            },
            required: ['workflow_id', 'inputs'],
          },
        },
      ],
    }));
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool 'executes' a workflow, implying a write operation, but doesn't describe what execution involves (e.g., triggering a process, side effects, permissions required, or response format). This leaves significant gaps in understanding the tool's behavior beyond basic action.

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, efficient sentence with no wasted words. It's front-loaded with the core action, making it easy to parse. However, it could be more structured by including key details, but it earns high marks for brevity.

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 complexity of executing a workflow (a write operation with potential side effects), no annotations, no output schema, and incomplete behavioral disclosure, the description is inadequate. It doesn't explain what happens upon execution, error handling, or return values, leaving critical context gaps for effective tool use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the two parameters ('workflow_id' and 'inputs'). The description adds minimal value by mentioning 'required inputs', which aligns with the schema but doesn't provide additional meaning, syntax, or format details beyond what's already structured.

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 states the action ('execute') and resource ('workflow'), but it's vague about what execution entails. It doesn't distinguish from siblings like 'get_workflow_inputs' or 'list_workflows', which are related but different operations. The purpose is understandable but lacks specificity about the execution mechanism or outcome.

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 (e.g., needing workflow inputs from 'get_workflow_inputs'), exclusions, or how it differs from other tools like 'ask_assistant'. The description offers no contextual usage information.

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/folderr-tech/folderr-mcp-server'

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