Linked API MCP

execute_custom_workflow

Execute custom LinkedIn automation workflows by providing a workflow definition. Automate tasks such as lead searching, messaging, and profile analysis through AI assistants.

Instructions

Execute a custom workflow definition

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "definition": "<definition>"
    },
    "name": "execute_custom_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`definition`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 23, 2025

TDQS

C2.1/5.0

Behavior2/5

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

Annotations are absent, so the description must fully disclose behavior. It only says 'execute', omitting side effects, permissions, rate limits, or any consequences. The agent has no way to know what the tool actually does beyond the vague term.

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

Conciseness3/5

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

The description is a single sentence with no extraneous words, achieving conciseness. However, it is under-specified, sacrificing substance for brevity. It does not earn its keep by providing useful information.

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

Completeness1/5

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

Given no output schema and no parameter documentation, the description is critically incomplete. It fails to explain what the workflow does, what results are returned, or any constraints on the definition object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'definition' is an object with no description in either the schema (coverage 0%) or the description. The description adds no meaning about its structure, constraints, or required properties, leaving the agent to guess.

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 a verb ('Execute') and a resource ('custom workflow definition'), but provides no specifics about what a workflow definition is or what execution entails. It does not differentiate from sibling tools like get_workflow_result, leaving ambiguity.

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 on when to use this tool versus alternatives (e.g., other workflow-related tools). The description lacks context on prerequisites, scenarios, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.