Skip to main content
Glama
Sign In
AutoManus MCP Server

AutoManus MCP Server

Official
by automanus-io
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

create_sales_agent

Create an AI sales agent that researches your website and deploys to WhatsApp and Webchat. Requires company name and email.

Instructions

Create an AI sales agent for a business. Researches the website automatically and deploys to WhatsApp and Webchat. Ask the user for their email if not provided.

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

Input Schema

NameRequiredDescriptionDefault
emailNoUser email address for account creation and receiving the agent claim link. Ask the user for this.
company_nameYesBusiness/company name
website_urlNoWebsite URL to research. We analyze it to populate knowledge base.
agent_nameNoCustom agent name (optional, defaults to "{company} Assistant")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.6

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool researches the website automatically and deploys to WhatsApp and Webchat, which are key behaviors. However, it does not mention side effects (e.g., overwriting existing agents), authentication requirements, rate limits, or error conditions, leaving gaps.

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?

The description is two sentences, front-loaded with the main purpose and a practical usage hint. Every word contributes meaning with no redundancy or filler.

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?

With no output schema, the description should cover return values. It states deployment targets but does not explain what the user receives (e.g., agent ID, claim link), though the schema's email description partially covers that. Overall, it is sufficient for basic use but could be more complete.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds the note 'Ask the user for their email if not provided,' which reinforces the email parameter but does not provide significant new semantics beyond what the schema already describes.

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?

The description clearly states the tool creates an AI sales agent, with specific actions: 'Researches the website automatically and deploys to WhatsApp and Webchat.' This differentiates it from siblings add_knowledge and generate_qr_code, which have distinct purposes.

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?

The description implicitly indicates usage when creating a sales agent, and adds guidance to 'Ask the user for their email if not provided.' However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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

Deploy Server

Other Tools