Lenx MCP Server

lenx_create_task

Set up social media monitoring tasks: live tasks run continuously; adhoc tasks collect data within a defined time range. Configure search queries and language.

Instructions

Create a new monitoring task (live or adhoc). Live tasks run continuously; adhoc tasks require a date_range.

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": {
      "task_type": "<task_type>",
      "task_name": "<task_name>",
      "language": "<language>",
      "search_query": "<search_query>"
    },
    "name": "lenx_create_task"
  }
}

Input Schema

Name	Required	Description
`task_type`	Yes	Task type: 'live' runs continuously, 'adhoc' requires date_range
`task_name`	Yes	Task name (1-50 characters)
`language`	Yes	Language: zh-t (Traditional Chinese), zh-s (Simplified Chinese), en (English)
`date_range`	No	Required for adhoc tasks: time range for data collection
`search_query`	Yes	Search query configuration. Example query_layer with nested grouped keywords: [{"in": ["brand_name", "product_name"], "ex": ["competitor_name"]}] Nested OR-group form: [{"in": [["brand_name", "brand_alias"], ["product_series_a", "product_series_b"]], "ex": [["competitor_a", "competitor_b"]]}]

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 17, 2026

TDQS

A3.9/5.0

Behavior2/5

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

With no annotations, the description should disclose key behavioral traits. It states the tool creates a task but does not mention side effects, authentication needs, rate limits, or what happens upon creation (e.g., returns task ID). The description is basic and leaves important behavior undocumented.

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 a single, direct sentence that conveys the core purpose and key distinction. No extraneous information; every part earns its place.

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?

The input schema is fully documented, but there is no output schema. The description does not mention what the tool returns (e.g., task ID, status). For a create operation, this is a gap. However, given the input schema completeness, it is minimally adequate.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the semantics of task_type (live vs adhoc) and that date_range is required for adhoc. This goes beyond the schema's enum descriptions and clarifies conditional requirements.

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 'Create a new monitoring task' and distinguishes between live and adhoc types. It uses a specific verb and resource, and the purpose is unambiguous. It differentiates from siblings (e.g., delete, update) which perform other actions.

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

Usage Guidelines4/5

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

The description provides clear context for when to use live vs adhoc tasks: 'Live tasks run continuously; adhoc tasks require a date_range.' While it does not explicitly mention when not to use or alternatives, the guidance is sufficient for a typical agent.

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

Deploy Server