Skip to main content
Glama
punkpeye

HiveFlow MCP Server

list_flows

Retrieve and filter user workflows from HiveFlow automation platform by status and limit results for management.

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 handler function for the 'list_flows' tool. It constructs query parameters from input args (status and limit), fetches the list of flows from the HiveFlow API, formats them into a bullet-point text list, and returns the response in MCP format.
    private async listFlows(args: any) {
      const params: any = {};
      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.flows || [];
      
      const flowsList = flows.map((flow: any) => 
        `• ${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'}`
          }
        ]
      };
    }
  • Input schema for the 'list_flows' tool, defining optional parameters: status (enum of flow states) and limit (number, default 50). Used for validation in tool calls.
    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.ts:80-98 (registration)
    Registration of the 'list_flows' tool in the MCP server's listTools response, including name, description, and input schema.
    {
      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.ts:225-226 (registration)
    Dispatch/registration in the switch statement of the CallToolRequestSchema handler that routes 'list_flows' calls to 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it lists flows but doesn't describe return format, pagination, authentication needs, rate limits, or whether it's read-only. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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 in Spanish that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 listing flows with parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned, how results are structured, or any behavioral traits, making it inadequate for an agent to fully understand the tool's operation.

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 schema description coverage is 100%, with clear descriptions for both parameters ('status' and 'limit'), including an enum for 'status' and a default for 'limit'. The description adds no parameter information beyond what the schema provides, so it meets the baseline for high coverage without compensating value.

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 'Lista todos los flujos de trabajo del usuario' clearly states the verb ('Lista') and resource ('flujos de trabajo del usuario'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_flow' or 'get_flow_executions', which might also retrieve flow information, so it misses full sibling distinction.

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 doesn't mention when to choose 'list_flows' over 'get_flow' or 'get_flow_executions', nor does it specify any prerequisites or exclusions, leaving usage context unclear.

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

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