Skip to main content
Glama
punkpeye

HiveFlow MCP Server

get_flow_executions

Retrieve execution history for a specific workflow to monitor performance and track automation results. Use this tool to analyze past runs and identify patterns in your automated processes.

Instructions

Obtiene el historial de ejecuciones de un flujo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesID del flujo
limitNoLímite de resultados

Implementation Reference

  • The handler function that implements the get_flow_executions tool logic. It makes an HTTP GET request to the HiveFlow API endpoint `/api/flows/{flowId}/executions` with optional limit parameter, processes the executions list, formats it as a bullet-point text string, and returns it in the MCP response format.
    private async getFlowExecutions(args: any) {
      const response = await this.hiveflowClient.get(`/api/flows/${args.flowId}/executions`, {
        params: { limit: args.limit || 10 }
      });
      const executions = response.data.executions || [];
      
      const executionsList = executions.map((exec: any) => 
        `• ${exec.id} - Estado: ${exec.status} - ${exec.createdAt}`
      ).join('\n');
      
      return {
        content: [
          {
            type: 'text',
            text: `📈 Ejecuciones del flujo (${executions.length}):\n\n${executionsList || 'No hay ejecuciones'}`
          }
        ]
      };
    }
  • The schema definition for the get_flow_executions tool, including input schema specifying required flowId (string) and optional limit (number, default 10). This is returned in the ListTools response.
    {
      name: 'get_flow_executions',
      description: 'Obtiene el historial de ejecuciones de un flujo',
      inputSchema: {
        type: 'object',
        properties: {
          flowId: {
            type: 'string',
            description: 'ID del flujo'
          },
          limit: {
            type: 'number',
            description: 'Límite de resultados',
            default: 10
          }
        },
        required: ['flowId']
      }
    }
  • src/index.ts:239-240 (registration)
    The switch case registration/dispatch in the CallToolRequestSchema handler that calls the getFlowExecutions method when the tool 'get_flow_executions' is invoked.
    case 'get_flow_executions':
      return await this.getFlowExecutions(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. While 'obtiene' (gets) implies a read operation, the description doesn't address important behavioral aspects: whether this requires specific permissions, what format the history returns (timestamps, statuses, errors), if results are paginated beyond the 'limit' parameter, or if there are rate limits. For a historical data retrieval tool with zero annotation coverage, this is insufficient.

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 language or unnecessary elaboration. However, being in a different language than the schema (English) could create minor comprehension issues for some agents, slightly reducing effectiveness.

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 no annotations and no output schema, the description is incomplete for a tool that retrieves historical execution data. It doesn't explain what constitutes an 'execution' in this context, what data points are returned, whether results are sorted, or how historical data is organized. For a tool that presumably returns potentially complex execution records, 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 both parameters (flowId, limit) are documented in the schema. The description doesn't add any parameter semantics beyond what the schema provides - it mentions 'un flujo' (a flow) which aligns with flowId, but doesn't explain format expectations or provide context about the limit parameter's effect. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('obtiene el historial de ejecuciones') and resource ('de un flujo'), which translates to 'gets the execution history of a flow'. It's specific about retrieving historical data rather than current state or creating flows. However, it doesn't explicitly distinguish from sibling tools like 'get_flow' (which might get flow metadata) or 'execute_flow' (which triggers new 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. There are several sibling tools for flow management (create_flow, execute_flow, get_flow, pause_flow, resume_flow), but the description doesn't indicate when historical execution data is needed versus current flow status or metadata. No exclusions or prerequisites 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/punkpeye/hiveflow-mcp-server'

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