Skip to main content
Glama
hiveflowai

HiveFlow MCP Server

Official
by hiveflowai

list_flows

Retrieve and filter user workflows from the HiveFlow automation platform by status, enabling management of automation flows through AI assistants.

Instructions

Lista todos los flujos de trabajo del usuario

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFiltrar por estado del flujo (opcional)
limitNoLímite de resultados (opcional)

Implementation Reference

  • The main handler function for the 'list_flows' tool. It constructs query parameters from input args, fetches the list of flows from the HiveFlow API endpoint '/api/flows', formats them into a bullet-point text list, and returns a formatted text response.
    async listFlows(args) {
      const params = {};
      if (args.status) params.status = args.status;
      if (args.limit) params.limit = args.limit;
    
      const response = await this.hiveflowClient.get('/api/flows', { params });
      const flows = response.data.data || [];
      
      const flowsList = flows.map(flow => 
        `• ${flow.name} (${flow._id}) - Estado: ${flow.status || 'draft'}`
      ).join('\n');
      
      return {
        content: [
          {
            type: 'text',
            text: `📋 Flujos encontrados (${flows.length}):\n\n${flowsList || 'No hay flujos disponibles'}`
          }
        ]
      };
    }
  • src/index.js:71-89 (registration)
    The tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema for the 'list_flows' tool.
    {
      name: 'list_flows',
      description: 'Lista todos los flujos de trabajo del usuario',
      inputSchema: {
        type: 'object',
        properties: {
          status: {
            type: 'string',
            enum: ['active', 'paused', 'stopped', 'draft'],
            description: 'Filtrar por estado del flujo (opcional)'
          },
          limit: {
            type: 'number',
            description: 'Límite de resultados (opcional)',
            default: 50
          }
        }
      }
    },
  • src/index.js:216-217 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches calls to the 'list_flows' tool by invoking the listFlows method.
    case 'list_flows':
      return await this.listFlows(args);
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. While 'list' implies a read operation, it doesn't specify whether this requires authentication, what permissions are needed, whether results are paginated (beyond the optional limit parameter), or what format the output takes. For a listing tool with zero annotation coverage, this is insufficient behavioral context.

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 in Spanish that directly states the tool's purpose. There's no wasted verbiage or unnecessary elaboration. While it could be more specific about scope, it's appropriately concise for a basic listing tool description.

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 listing tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'all workflows' means in context, doesn't mention authentication requirements, doesn't describe output format, and provides no guidance on when to use this versus sibling tools. The description should do more to compensate for the lack of structured metadata.

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?

The description mentions no parameters at all. However, with 100% schema description coverage, both parameters ('status' and 'limit') are well-documented in the schema with descriptions and enum values. The baseline score of 3 is appropriate when the schema does the heavy lifting, though the description adds no additional parameter context beyond what's already in the structured schema.

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 'Lista todos los flujos de trabajo del usuario' which translates to 'Lists all user workflows'. This clearly identifies the verb ('list') and resource ('workflows'), but it's vague about scope - 'all' could mean all workflows in the system or just the current user's workflows. It doesn't distinguish this tool from sibling tools like 'get_flow' or 'get_flow_executions'.

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. With siblings like 'get_flow' (for individual workflows), 'get_flow_executions' (for execution history), and 'list_mcp_servers' (for server listing), there's no indication of when this bulk listing tool is preferred over more specific queries. No usage context or exclusions are mentioned.

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