wecom-crm-mcp

wecom_acquisition

Create and manage customer acquisition links, track linked customers, and monitor quota and statistics to optimize lead generation in WeCom CRM.

Instructions

获客助手 — actions: create_link / list_links / get_link / update_link / delete_link / list_customers / get_quota / get_statistic.

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

Input Schema

Name	Required	Description	Default
`action`	Yes
`params`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No behavioral traits (e.g., destructiveness, read-only, side effects) are disclosed. The description only lists actions without indicating consequences or requirements. Annotations are absent, so the description carries full burden but fails.

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

Conciseness2/5

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

The description is extremely concise, but this is under-specification rather than efficient communication. It lacks necessary structure and depth.

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

Completeness1/5

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

Despite having an output schema, the description does not explain return values, action purposes, or parameter usage. For a multi-action tool, this is severely incomplete.

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

Parameters2/5

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

The description lists valid values for the 'action' parameter, which adds some guidance beyond the schema. However, it does not explain the 'params' object or the semantics of each action, leaving parameter meaning unclear. Schema coverage is 0%.

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

Purpose2/5

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

The description identifies the tool as '获客助手' (Acquisition Assistant) and lists available actions, but does not clarify what acquisition means in this context or how it differs from sibling tools like wecom_contact_way or wecom_customer. The purpose is vague.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives, nor any conditions for use. The description lacks any usage context.

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

Deploy Server