Smartlead Simplified MCP Server

smartlead_update_campaign_settings

Update campaign name, status, and additional settings by providing the campaign ID.

Instructions

Update a campaign's general settings.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "smartlead_update_campaign_settings"
  }
}

Input Schema

Name	Required	Description
`name`	No	New name for the campaign
`status`	No	Status of the campaign
`settings`	No	Additional campaign settings
`campaign_id`	Yes	ID of the campaign to update

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and description only says 'update' without disclosing behavioral traits like idempotency, permission requirements, or side effects. The description fails to compensate for missing annotations.

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?

Single sentence is concise and front-loaded, but could benefit from a brief expansion on scope of 'general settings' without losing efficiency.

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?

With 4 parameters including a nested object and no output schema, the description is too sparse. It fails to explain what 'general settings' encompasses or what the response looks like.

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 covers 100% of parameters with descriptions. The description adds no value beyond schema, so baseline score of 3 is appropriate.

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?

Description clearly states the tool updates campaign general settings. However, it does not distinguish from sibling tools like smartlead_update_campaign_status or smartlead_update_campaign_schedule, which could lead to confusion.

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. Given siblings for status and schedule updates, explicit usage context is missing.

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