swarmix-mcp

create_product

Create a new product or business profile for automated outreach campaigns by analyzing its website to understand value proposition and target audience.

Instructions

Create a new product/business to manage outreach for. The AI will analyze the website to learn the value proposition and audience.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Product or business name
`domain`	No	Website domain (e.g., "mycoaching.com")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It successfully reveals the critical side effect: 'The AI will analyze the website to learn the value proposition and audience.' This explains what happens beyond simple record creation. However, it lacks standard mutation safety details (idempotency, reversibility, error conditions) expected when no annotations exist.

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 with zero waste. Front-loaded with the specific action ('Create a new product/business') followed immediately by the purpose clause ('to manage outreach for'). The second sentence efficiently explains the AI analysis mechanism without redundancy.

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 parameter complexity (2 simple params), but gaps remain for a creation tool. With no output schema and no annotations, the description should ideally indicate what identifies the created resource or success indicators. The domain parameter is optional (only name is required), but the description implies website analysis always occurs—a subtle gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% description coverage (baseline 3). The description adds significant value by explaining the behavioral semantics of the 'domain' parameter: it triggers AI analysis of the website to extract 'value proposition and audience.' This context helps the agent understand why to provide a domain and what data format is expected, going beyond the schema's simple 'Website domain' description.

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 specific verb ('Create') and resource ('product/business'). The 'to manage outreach for' clause adds specific context. However, the conflation of 'product/business' creates ambiguity with the sibling tool 'setup_business,' making it unclear which tool handles business-level vs. product-level creation. Distinguishes adequately from other siblings like 'create_agent.'

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 explicit guidance on when to use this versus the sibling 'setup_business' (given the description mentions both product and business). No mention of when the optional 'domain' parameter should be provided vs. omitted. Usage is only implied by the phrase 'to manage outreach for.'

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

Deploy Server