Leadpoet

Create a draft campaign

createCampaign

Idempotent

Useful when the user wants to start a cold email or LinkedIn outreach campaign. Creates a new draft campaign from a saved audience, sender accounts and campaign settings. The draft does not send until it is launched. Retrying with the same idempotencyKey and input returns the first result instead of repeating the action.

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": {
      "body": "<body>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "createCampaign"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes
`idempotencyKey`	Yes	A unique key for this action. Reuse it only to retry the same call with the same input; use a new key for a new action.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety and idempotency hints, but the description adds the meaningful operational fact that the resulting campaign is inert until launched, and spells out the retry contract (same key + same input returns the first result). It omits any mention of required account/audience prerequisites or quotas, which matter for a creation call with caps like 20 accounts and 2000 contacts.

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?

Three short sentences, front-loaded with the trigger condition, then the action, then the two behavioral caveats. No filler or restatement of the title beyond what is needed.

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?

For a tool whose single 'body' parameter hides a deep nested object graph and which has no output schema, the description never indicates what comes back (presumably a campaign id/status) or what a 'saved audience' snapshot must be. It is adequate for choosing the tool but thin for invoking it confidently on complex payloads.

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 coverage is 50% and only idempotencyKey carries an inline description, but the body schema is highly self-documenting through enums, consts, and bounds. The description loosely maps to the three required fields (audience, sender accounts, settings) yet says nothing about the nested 'plays' structure or the copilot/autopilot mode, which are the least self-evident parts of the payload.

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 ("Creates a new draft campaign") plus the three inputs it is built from (saved audience, sender accounts, campaign settings). This separates it cleanly from siblings like createAudience, createIcp, and previewCampaign without needing to open any schema.

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

Usage Guidelines4/5

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

Opens with an explicit trigger condition: use when the user wants to start a cold email or LinkedIn outreach campaign. It also implies the boundary with launching ("does not send until it is launched"), but never names an alternative tool or a when-not case, so an agent must infer that pausing/updating/launching are separate calls.

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

All Leadpoet tools Inspect

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

Need Help?