flowforge-mcp

flowforge_update_campaign_settings

Idempotent

Patches only the campaign settings you specify—assistant, caller number or pool, schedule, dialer, compliance, voicemail drop, webhook, pacing, or branch—so live updates avoid overwriting untouched fields.

Instructions

Patch a campaign's settings: assistant, caller number/pool, schedule, dialer and compliance rules, voicemail drop, webhook, pacing, branch. Only the keys you pass change.

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_update_campaign_settings"
  }
}

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.4/5.0

Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior. The description adds one real behavioral fact beyond them: unspecified settings are left untouched. It does not say whether nested sections like schedule or dialer_settings are merged or replaced, nor what happens on invalid keys, which matters for a partially-typed settings object.

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?

Two sentences, front-loaded with the action and scope, then the key behavioral rule. No filler, though the long comma-separated category list is dense and could be grouped.

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 explanation, and the annotations cover the safety profile. What remains missing is how nested sub-objects interact with the patch (merge depth) and where to look up the full settings schema, which the input schema only gestures at via flowforge_api_reference.

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 already enumerates acceptable settings keys and documents campaign_id and response_format. The description's 'only the keys you pass change' clarifies the semantics of the settings object, but nested merge-vs-replace behavior is left ambiguous and no format details are added.

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?

States a specific verb and resource ('Patch a campaign's settings') and enumerates the setting categories affected (assistant, caller number/pool, schedule, dialer, compliance, voicemail, webhook, pacing, branch). An agent can distinguish it from flowforge_get_campaign or flowforge_create_campaign, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The sentence 'Only the keys you pass change' gives an important usage cue about PATCH-style partial updates, implying it is the tool to use for modifying a subset of settings. There is no explicit guidance on when to prefer this over flowforge_api_reference or flowforge_control_campaign, nor any mention of prerequisites.

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

Deploy Server