Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_search_mp_image_posts

Read-only

按关键词搜索公众号贴图,支持综合、最新、最热排序与分页。

将结果的 article_url 作为 url 传给 wechat_get_mp_article_detail_by_url 获取正文和全部图片, 或传给 wechat_get_mp_article_comments_by_url 获取评论。搜索卡片可能包含正文片段,精确标题和发布时间以详情为准。

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

Input Schema

NameRequiredDescriptionDefault
keywordYes公众号贴图搜索词,例如城市摄影、光谷书房;不要传链接或账号 ID。
sort_typeNogeneral 综合、time_descending 最新、hot 最热。general
page_tokenNo首次留空;翻页原样传回 next_page_token,保持 keyword 和 sort_type 不变。请在 3 天内续页;令牌失效后需重新搜索。

Output Schema

NameRequiredDescriptionDefault
itemsYes本页公众号贴图搜索结果
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页分页令牌;空字符串表示已结束,应停止翻页;非空时完整原样传回 page_token,并保持 keyword 和 sort_type 不变。请在 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: +"WechatMpImagePostSearchItemData"
    • 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: +"WechatMpImagePostSearchResult"
  4. Changed3 schema fields changed
    • changedOutput schema / properties / items / items / properties / article_url / description
      Previous value: -"公众号贴图链接"New value: +"公众号贴图链接;作为 url 传给 wechat_get_mp_article_detail_by_url 获取正文和图片,也可用于评论查询"
    • 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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context by warning that search cards may only contain body snippets and that exact title and publish time must come from the detail endpoint. This sets correct expectations about result fidelity, which the annotations and output schema do not convey. It stops short of describing paging limits or result-count behavior at the search level.

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?

Two short paragraphs: the first front-loads purpose, the second the required follow-up workflow. Every sentence carries actionable information, with no filler or repetition of the schema.

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

Completeness5/5

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

Search tool with an existing output schema and read-only annotations, and the description covers purpose, sort/paging capability, result-fidelity caveats, and the exact follow-up calls needed to get full content. Nothing an agent needs in order to select and chain this tool is missing.

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%, including the sort enum values and the page_token round-trip and 3-day expiry rule, so the schema already carries parameter meaning. The description only restates that sorting (综合/最新/最热) and pagination exist, adding no syntax or constraint beyond the schema. Baseline 3 is appropriate here.

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?

States a specific verb and resource (按关键词搜索公众号贴图) plus the supported sort modes and pagination, which tells an agent exactly what class of entity it searches. It is implicitly distinguished from siblings like wechat_search_mp_articles and wechat_get_mp_account_image_posts_by_account_id by the resource name (贴图, keyword-based), but never names those alternatives, so differentiation is left to inference.

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?

Gives concrete downstream guidance: pass the returned article_url to wechat_get_mp_article_detail_by_url for full text and images, or to wechat_get_mp_article_comments_by_url for comments. That is clear when-next behavior, but there is no guidance on when to prefer this keyword search over the account-scoped image-post listing or the general article search, and no note on quota/cost.

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