Skip to main content
Glama
hiveflowai

HiveFlow MCP Server

Official
by hiveflowai

execute_flow

Execute a specific workflow in HiveFlow automation platform using its ID, with optional inputs to trigger automated processes.

Instructions

Ejecuta un flujo de trabajo especĂ­fico

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo a ejecutar
inputsNoInputs opcionales para el flujo

Implementation Reference

  • The executeFlow handler function that POSTs to the HiveFlow API to execute the specified flow with optional inputs and returns a success message with execution details.
    async executeFlow(args) {
      const response = await this.hiveflowClient.post(`/api/flows/${args.flowId}/execute`, {
        inputs: args.inputs || {}
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `🚀 Flujo ejecutado exitosamente.\nExecution ID: ${response.data.executionId || 'N/A'}\nEstado: ${response.data.status || 'iniciado'}`
          }
        ]
      };
    }
  • Input schema defining the parameters for the execute_flow tool: required flowId (string) and optional inputs (object).
    inputSchema: {
      type: 'object',
      properties: {
        flowId: {
          type: 'string',
          description: 'ID del flujo a ejecutar'
        },
        inputs: {
          type: 'object',
          description: 'Inputs opcionales para el flujo'
        }
      },
      required: ['flowId']
    }
  • src/index.js:104-121 (registration)
    Registration of the execute_flow tool in the ListTools response, including name, description, and input schema.
    {
      name: 'execute_flow',
      description: 'Ejecuta un flujo de trabajo especĂ­fico',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo a ejecutar'
          },
          inputs: {
            type: 'object',
            description: 'Inputs opcionales para el flujo'
          }
        },
        required: ['flowId']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Ejecuta' implies a write/mutation operation, but the description doesn't reveal whether this is synchronous/asynchronous, what permissions are needed, whether it's idempotent, what happens on failure, or any rate limits. It provides minimal behavioral context beyond the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient Spanish sentence with zero wasted words. It's appropriately sized and front-loaded with the core action. Every word earns its place in conveying the basic purpose.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what execution means, what the expected outcome is, error conditions, or how this interacts with sibling tools. Given the complexity implied by 'execute' and lack of structured behavioral data, more context is needed.

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 already documents both parameters (flowId and inputs) adequately. The description adds no additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 'Ejecuta un flujo de trabajo especĂ­fico' clearly states the action (execute) and resource (workflow), but it's vague about what execution entails and doesn't differentiate from sibling tools like pause_flow or resume_flow. It provides basic purpose but lacks specificity about what 'execute' means 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 about when to use this tool versus alternatives like pause_flow, resume_flow, or get_flow_executions. The description doesn't mention prerequisites (e.g., needing an existing flow), exclusions, or contextual factors that would help an agent choose appropriately among siblings.

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/hiveflowai/hiveflow-mcp-server'

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