Skip to main content
Glama

SocialDataX 红果 Hongguo MCP

hongguo_search_general

Read-only

按关键词综合搜索红果剧集、影片和图文帖子,支持内容类型筛选和分页;返回精简业务信息,聚合结果已展开。不提供独立剧集或视频页签搜索,也不解析播放地址。

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": "hongguo_search_general"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes红果综合搜索的关键词或短语,例如剧名、人物名或题材;最多200个字符,部分表情符号计为两个字符。不含控制字符;不要传链接、作品 ID 或分页令牌。
page_tokenNo首屏留空;续页将上一页完整 next_page_token 原样传回,不得修改或跨搜索复用。关键词和内容类型必须保持一致;有效期3天,原设备不可用时重新搜索。
content_typesNo内容类型可多选,不可重复。仅在用户明确限定内容类型时设置;未限定时省略或传空列表(不限),不要根据搜索关键词自行缩窄类型。live_action=真人剧,comic=漫剧(非静态漫画),ai_drama=红果平台单独列出的AI剧分类,film_tv=影视剧,short_video=短视频,image_text=图文。

Output Schema

NameRequiredDescriptionDefault
itemsYes搜索到的剧集、影片或图文帖子,通过type区分;剧集标识为series_id,图文标识为post_id。聚合卡已展开,同页相同类型、相同标识的结果仅保留首次出现的条目。按搜索顺序返回;未提供的可选信息为null或空列表,不代表数值为零。
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页不透明令牌。需要继续搜索时,将此值原样传入 page_token;空字符串表示分页结束。不要仅根据 items 是否为空判断结束。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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/openness profile is covered. The description adds useful behavioral context: it returns concise business information, aggregated results are expanded, and playback addresses are not resolved. It does not discuss auth or rate limits, which is acceptable with annotations present.

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 front-loaded sentence with semicolon-separated clauses. It includes useful scope and exclusions without filler or redundant restatement of the schema.

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?

For a search tool with an output schema, rich annotations, and fully described parameters, the description covers the essential scope, result style, and limitations. It is complete enough for correct selection and invocation, though it does not mention ordering or ranking behavior.

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 all three parameters are fully documented in the schema, including keyword limits, page_token continuation rules, and content_types enum values. The description only generally mentions content-type filtering and pagination, so it adds no meaningful parameter semantics beyond the schema.

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 states a specific verb and resource set: keyword-based comprehensive search across Hongguo series, films, and image-text posts. It also defines scope through content-type filtering and pagination, and explicitly excludes independent series/video tab search and playback-address parsing.

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?

Usage is clear for keyword-based comprehensive search, with explicit exclusions for independent tab searches and playback-address parsing. It does not name an alternative tool or say when to prefer detail-oriented siblings, but the context and exclusions are strong.

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