swarmix-mcp

create_agent

Create an AI outreach agent for LinkedIn, Email, X, Instagram, or Blog channels to automate client acquisition for specific products.

Instructions

Create a new AI outreach agent for a specific channel. Requires a product ID. Available platforms: linkedin, email, x, instagram, blog.

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": {
      "productId": "<productId>",
      "name": "<name>",
      "platform": "<platform>"
    },
    "name": "create_agent"
  }
}

Input Schema

Name	Required	Description
`productId`	Yes	Product ID to create the agent for
`name`	Yes	Agent name
`platform`	Yes	Platform: linkedin, email, x, instagram, or blog

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Identifies the write operation ('Create') and platform constraints, but omits lifecycle state after creation (configured vs. running), idempotency behavior, or failure modes when productId is invalid.

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 tightly focused sentences. First states purpose, second lists requirements/constraints. No redundancy or wasted words despite the null title.

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?

Adequate for the input complexity (3 simple parameters) but lacks mention of return values or side effects. Given sibling tools暗示 an agent lifecycle (run/pause/resume), the description should clarify that this only creates configuration rather than activating the agent.

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 has 100% coverage with complete descriptions for all three parameters. Description reinforces the platform enum values and requirement of productId, but adds minimal semantic depth beyond what the schema already provides.

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?

Clear verb ('Create') and resource ('AI outreach agent') with scope ('for a specific channel'). Distinct from sibling operations like run_agent, pause_agent, and create_product, though it doesn't explicitly clarify whether the created agent starts in an active or inactive state.

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?

States prerequisite ('Requires a product ID') implying dependency on create_product, but lacks explicit workflow guidance (e.g., create_product → create_agent → run_agent) or conditions when NOT to use (e.g., if agent already exists).

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

Deploy Server