Skip to main content
Glama
Linked-API
by Linked-API

get_workflow_result

Retrieve results from background workflows in Linked API MCP server. Use this tool to monitor ongoing operations while maintaining client responsiveness.

Instructions

CONTINUE LISTENING TO BACKGROUND WORKFLOW - THIS IS NORMAL OPERATION! Background workflows are OPTIMAL BEHAVIOR for Linked API operations and keep the MCP client responsive. When a workflow runs in the background, this tool should be used with the provided workflowId and operationName parameters to continue listening for updates. The workflow continues processing in the background while you wait. This is the STANDARD way Linked API works - background processing provides optimal user experience!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe workflow ID provided in the background workflow status message
operationNameYesOptional function name for proper type restoration (provided in background workflow status if available)

Implementation Reference

  • The execute method of GetWorkflowResultTool that handles the tool invocation by retrieving the operation and executing it with progress tracking.
    public override async execute({
      linkedapi,
      args: { workflowId, operationName },
      workflowTimeout,
      progressToken,
    }: {
      linkedapi: LinkedApi;
      args: IGetWorkflowResultParams;
      workflowTimeout: number;
      progressToken?: string | number;
    }): Promise<TMappedResponse<unknown>> {
      const operation = linkedapi.operations.find(
        (operation) => operation.operationName === operationName,
      )!;
      return await executeWithProgress(this.progressCallback, operation, workflowTimeout, {
        workflowId,
        progressToken,
      });
    }
  • Zod schema defining the input parameters for validation: workflowId (string) and operationName (enum from OPERATION_NAME).
    protected readonly schema = z.object({
      workflowId: z.string(),
      operationName: z.enum(Object.values(OPERATION_NAME)),
    });
  • The getTool method returns the MCP Tool object including name, description, and inputSchema for the get_workflow_result tool.
    public override getTool(): Tool {
      return {
        name: this.name,
        description:
          'CONTINUE LISTENING TO BACKGROUND WORKFLOW - THIS IS NORMAL OPERATION! Background workflows are OPTIMAL BEHAVIOR for Linked API operations and keep the MCP client responsive. When a workflow runs in the background, this tool should be used with the provided workflowId and operationName parameters to continue listening for updates. The workflow continues processing in the background while you wait. This is the STANDARD way Linked API works - background processing provides optimal user experience!',
        inputSchema: {
          type: 'object',
          properties: {
            workflowId: {
              type: 'string',
              description: 'The workflow ID provided in the background workflow status message',
            },
            operationName: {
              type: 'string',
              description:
                'Optional function name for proper type restoration (provided in background workflow status if available)',
            },
          },
          required: ['workflowId', 'operationName'],
        },
      };
    }
  • The LinkedApiTools constructor registers GetWorkflowResultTool by instantiating it and adding to the tools array, which is later exposed via the MCP server.
    this.tools = [
      // Standard tools
      new SendMessageTool(progressCallback),
      new GetConversationTool(progressCallback),
      new CheckConnectionStatusTool(progressCallback),
      new RetrieveConnectionsTool(progressCallback),
      new SendConnectionRequestTool(progressCallback),
      new WithdrawConnectionRequestTool(progressCallback),
      new RetrievePendingRequestsTool(progressCallback),
      new RemoveConnectionTool(progressCallback),
      new SearchCompaniesTool(progressCallback),
      new SearchPeopleTool(progressCallback),
      new FetchCompanyTool(progressCallback),
      new FetchPersonTool(progressCallback),
      new FetchPostTool(progressCallback),
      new ReactToPostTool(progressCallback),
      new CommentOnPostTool(progressCallback),
      new CreatePostTool(progressCallback),
      new RetrieveSSITool(progressCallback),
      new RetrievePerformanceTool(progressCallback),
      // Sales Navigator tools
      new NvSendMessageTool(progressCallback),
      new NvGetConversationTool(progressCallback),
      new NvSearchCompaniesTool(progressCallback),
      new NvSearchPeopleTool(progressCallback),
      new NvFetchCompanyTool(progressCallback),
      new NvFetchPersonTool(progressCallback),
      // Other tools
      new ExecuteCustomWorkflowTool(progressCallback),
      new GetWorkflowResultTool(progressCallback),
      new GetApiUsageTool(progressCallback),
    ];
  • The LinkedApiMCPServer exposes all tools, including get_workflow_result, via getTools() for MCP registration.
    public getTools(): Tool[] {
      return this.tools.tools.map((tool) => tool.getTool());
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains that this is a monitoring/status-checking tool for background workflows, describes the background processing behavior ('workflow continues processing in the background while you wait'), and emphasizes this is normal operation for optimal user experience. It doesn't cover error conditions, rate limits, or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is overly verbose and repetitive with excessive capitalization and exclamation points. It repeats concepts like 'background workflows are optimal behavior' and 'standard way Linked API works' multiple times. While the core information is present, it could be conveyed in half the length with better structure and less emphasis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with no annotations and no output schema, the description provides adequate context about the tool's purpose and usage. However, it doesn't explain what kind of updates to expect, how long to listen, what success/failure states look like, or provide examples. Given the complexity of background workflow monitoring, more operational details would be helpful.

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 thoroughly. The description adds context about when these parameters are provided ('provided in background workflow status message'), but doesn't add significant semantic meaning beyond what the schema provides. The baseline of 3 is appropriate given the comprehensive schema coverage.

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 tool's purpose: to continue listening for updates on background workflows using workflowId and operationName parameters. It specifies the verb ('continue listening') and resource ('background workflow'), though it doesn't explicitly differentiate from sibling tools like 'execute_custom_workflow' or 'get_api_usage'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: when a workflow runs in the background, with the provided workflowId and operationName parameters. It explains this is the standard way Linked API works for optimal user experience, though it doesn't explicitly mention when NOT to use it or name specific alternatives.

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/Linked-API/linkedapi-mcp'

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