flowforge-mcp

flowforge_add_campaign_leads

Bulk-add contacts to a campaign by passing a campaign ID and lead list; manage duplicates and self-dial numbers, then receive a summary of added leads.

Instructions

Bulk-add leads (contacts) to a campaign.

Args: params: campaign_id and a leads array of contact objects.

Returns: The API result summarizing how many leads were added.

Error Handling: Returns "Error: ..." on failure.

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": {
      "params": "<params>"
    },
    "name": "flowforge_add_campaign_leads"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the response summary shape and the error-string convention, which is genuinely useful. It does not, however, disclose partial-failure semantics (what happens if some leads in the batch are rejected) or any batch-size limits, which matter for a non-idempotent bulk write.

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 purpose statement is front-loaded and the Args/Returns/Error Handling structure is easy to scan. The Args section largely restates the schema and is the only real waste, but the error-format sentence earns its place.

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?

An output schema exists, so return values need no further explanation, and the error convention is stated. For a bulk mutation tool, though, the description is silent on duplicate-skipping behavior, self-dial rejection, and partial-batch failure, which are exactly the edge cases an agent would need before invoking it.

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 only enumerates campaign_id and the leads array, omitting the optional allow_duplicates, allow_self_dial, and response_format flags. The signal reports 0% coverage at the top-level params wrapper, but the nested schema actually documents every field in detail, so the schema is doing the heavy lifting rather than the description.

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 opens with a specific verb and resource: "Bulk-add leads (contacts) to a campaign." That is unambiguous and implicitly contrasts with the sibling flowforge_remove_campaign_leads, though no sibling is named explicitly. An agent can identify the operation without opening the schema.

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?

There is no guidance on when to use this versus alternatives such as flowforge_start_batch_calls or flowforge_import_assistant, nor on prerequisites like the campaign needing to exist first. It also gives no advice on when to set allow_duplicates or allow_self_dial, which are precisely the decisions an agent would struggle with.

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

Deploy Server