wecom-crm-mcp

wecom_moment

Create, retrieve, cancel, and list customer moments tasks; fetch moment details and customer lists for targeted marketing in WeCom.

Instructions

客户朋友圈 — actions: add_moment_task / get_moment_task_result / cancel_moment_task / get_moment_list / get_moment_task / get_moment_customer_list.

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_moment"
  }
}

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

C2.9/5.0

Behavior2/5

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

The description does not disclose behavioral traits such as side effects, permission requirements, or rate limits. For example, 'cancel_moment_task' is likely destructive, but this is not mentioned. No annotations exist to supplement.

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

Conciseness4/5

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

The description is very short and front-loaded with the resource name, making it concise. However, it could be better structured: itemizing actions clearly or grouping them would improve readability.

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

Completeness2/5

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

Despite having an output schema and a list of actions, the description is incomplete for a multi-action tool. It fails to explain what each action does, what parameters are expected, or how to construct the 'params' object, leaving the agent guessing.

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 schema has 0% description coverage, leaving 'action' and 'params' undocumented. The description partially compensates by listing allowed action values, but it does not describe the structure of 'params' for each action, which is critical given the generic schema.

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?

The description names the resource ('客户朋友圈' / Customer Moments) and lists six specific actions, clearly indicating the tool's purpose for managing moments. However, it lacks a strong verb (e.g., 'Manage') and relies on the action list to convey purpose.

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 guidance is provided on when to use this tool versus siblings like wecom_customer or wecom_group_chat. The description merely lists actions without context 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