Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

Move lead to another campaign

move_lead_to_campaign

Moves a lead from one campaign to another: the lead's unsent emails in the source campaign are deleted, and if the target campaign is running, emails for the lead are enqueued there. Use it to re-route a lead into a better-fitting campaign.

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": {
      "sourceCampaignId": "<sourceCampaignId>",
      "leadId": "<leadId>",
      "targetCampaignId": "<targetCampaignId>"
    },
    "name": "move_lead_to_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYesThe numeric lead ID (returned when the lead was created)
sourceCampaignIdYesThe campaign the lead is currently in
targetCampaignIdYesThe campaign to move the lead into

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the supplied annotations by disclosing the two concrete side effects: unsent emails in the source campaign are deleted, and enqueueing in the target is conditional on that campaign running. Minor residual tension worth noting is that this disclosed deletion is an irreversible side effect while destructiveHint=false, though the lead record itself is not destroyed; permissions and return behavior remain unstated.

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

Conciseness5/5

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

Two sentences, both front-loaded with the operation and its effects before the use case. No filler, no repetition of the title, and the conditional behavior is packed into a compact clause.

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

Completeness4/5

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

For a three-parameter mutation tool with no output schema, the description covers what the agent most needs: the direction of the move and the side effects on both campaigns. What is missing is modest: required permissions, whether the lead's prior send/open history transfers, and the shape of the response.

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% and each parameter already documents its numeric lead/campaign ID and role, so the schema carries the semantics. The description's framing of source vs target adds only a little confirming context and no format or edge-case detail (e.g., what happens if source equals target).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with direction: 'Moves a lead from one campaign to another.' The added clause about unsent-email deletion and conditional re-enqueueing makes the effect concrete, and it is clearly distinguishable from sibling lead tools like update_lead or add_leads.

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?

'Use it to re-route a lead into a better-fitting campaign' gives a use case, so usage is more than implied. But it names no alternative (e.g., add_leads to place a lead in a second campaign without removing it) and states no when-not conditions, so an agent must infer the boundary cases itself.

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

All Emailchaser toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources