Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_search_mp_articles

Read-only

按搜索词查找微信公众号文章,支持排序、发布时间筛选和分页;不要传文章链接或公众号账号 ID。

读取全文时,将结果的 article_url 作为 url 传给 wechat_get_mp_article_detail_by_url; 查看指定公众号发布的文章请用 wechat_get_mp_account_articles_by_account_id。 搜索卡片的展示标题和发布时间可能与详情不同,精确值以详情为准。

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

Input Schema

NameRequiredDescriptionDefault
keywordYes公众号文章搜索词或关键词短语;例如量子位、人工智能。不要传文章链接或公众号账号 ID。
sort_typeNo排序方式:general(综合/相关性,默认)、time_descending(最新发布)、hot(最热,顺序以平台结果为准)。general
page_tokenNo公众号文章搜索分页令牌;首次留空,继续翻页原样传回 next_page_token,并保持 keyword、sort_type 和 publish_time_range 不变。请在 3 天内续页;令牌失效后需重新搜索。
publish_time_rangeNo发布时间范围:all(不限,默认)、day(最近一天)、week(最近七天)、half_year(最近半年)。all

Output Schema

NameRequiredDescriptionDefault
itemsYes本页公众号文章搜索结果
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword、sort_type 和 publish_time_range 不变。请在 3 天内续页;令牌失效后需重新搜索。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed11 schema fields changed
    • addedOutput schema / properties / items / items / properties / account_name / title
      Added value: +"Account Name"
    • addedOutput schema / properties / items / items / properties / article_url / title
      Added value: +"Article Url"
    • addedOutput schema / properties / items / items / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / items / items / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / items / items / properties / read_count_text / title
      Added value: +"Read Count Text"
    • addedOutput schema / properties / items / items / properties / summary / title
      Added value: +"Summary"
    • addedOutput schema / properties / items / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatMpArticleSearchItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"WechatMpArticleSearchResult"
  4. Changed2 schema fields changed
    • changedOutput schema / properties / items / items / properties / publish_time / description
      Previous value: -"发布时间,秒级 Unix 时间戳;不可用时为 null"New value: +"搜索源返回的发布时间,秒级 Unix 时间戳;可能与详情不同,精确发布时间以详情为准;不可用时为 null"
    • changedOutput schema / properties / items / items / properties / title / description
      Previous value: -"公众号文章标题"New value: +"搜索卡片展示标题;精确标题以文章详情为准"
  5. Changed2 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"公众号文章搜索分页令牌;首次留空,继续翻页原样传回 next_page_token,并保持 keyword、sort_type 和 publish_time_range 不变。"New value: +"公众号文章搜索分页令牌;首次留空,继续翻页原样传回 next_page_token,并保持 keyword、sort_type 和 publish_time_range 不变。请在 3 天内续页;令牌失效后需重新搜索。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword、sort_type 和 publish_time_range 不变。"New value: +"下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword、sort_type 和 publish_time_range 不变。请在 3 天内续页;令牌失效后需重新搜索。"
  6. Changed4 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"公众号文章搜索分页令牌;首次留空,继续翻页原样传回 next_page_token,并保持搜索词不变。"New value: +"公众号文章搜索分页令牌;首次留空,继续翻页原样传回 next_page_token,并保持 keyword、sort_type 和 publish_time_range 不变。"
    • addedInput schema / properties / publish_time_range
      Added value: +{
      +  "default": "all",
      +  "description": "发布时间范围:all(不限,默认)、day(最近一天)、week(最近七天)、half_year(最近半年)。",
      +  "enum": [
      +    "all",
      +    "day",
      +    "week",
      +    "half_year"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sort_type
      Added value: +{
      +  "default": "general",
      +  "description": "排序方式:general(综合/相关性,默认)、time_descending(最新发布)、hot(最热,顺序以平台结果为准)。",
      +  "enum": [
      +    "general",
      +    "time_descending",
      +    "hot"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword 不变。"New value: +"下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword、sort_type 和 publish_time_range 不变。"
  7. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: search-card titles and publish times may differ from the authoritative detail values, which warns the agent not to treat list output as ground truth. It does not mention cost/points consumption (there is a points-balance sibling) or rate limits.

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?

It is front-loaded with the core capability, then the exclusions, then the sibling handoffs — a sensible order. There is minor redundancy: the 'don't pass article links or account IDs' warning appears in both the description and the keyword schema field, and could have been stated once.

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 an output schema present, the description need not describe return values, and annotations cover safety. It supplies the routing, the pagination-handoff hint, and the title/time discrepancy caveat — enough for correct invocation. Missing only secondary operational details such as result limits or credit cost.

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?

Schema description coverage is 100%, and each parameter (keyword, sort_type, page_token, publish_time_range) is fully documented in the schema, so the schema carries the burden. The description only restates at a high level that sorting, publish-time filtering and pagination are supported, and the 'don't pass a URL or account ID' constraint for keyword is duplicated from the schema. Baseline 3 applies.

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 opens with a specific verb+resource: search WeChat public-account articles by keyword, and notes supported sort/publish-time/pagination. It explicitly names the two sibling tools that cover adjacent tasks (article detail by URL, account article listing), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

It gives both positive routing (use this for keyword search) and explicit exclusions ('不要传文章链接或公众号账号 ID'), plus a downstream handoff chain: take article_url from results and pass it to wechat_get_mp_article_detail_by_url. For per-account browsing it points to wechat_get_mp_account_articles_by_account_id. The only missing alternative is wechat_search_mp_image_posts, which is a minor omission.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources