Skip to main content
Glama
juhemcp

Juhe News MCP Server

Official
by juhemcp

get_news_list

Retrieve today's trending news headlines by category such as technology, sports, finance, or entertainment using pagination controls.

Instructions

通过新闻类型获取今日热点新闻头条

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo新闻类型:top(推荐,默认),guonei(国内),guoji(国际),yule(娱乐),tiyu(体育),junshi(军事),keji(科技),caijing(财经),youxi(游戏),qiche(汽车),jiankang(健康)
pageNo当前页数, 默认1, 最大50
page_sizeNo每页返回新闻条数, 默认20, 最大50

Implementation Reference

  • The main handler function for the 'get_news_list' tool. It constructs an API request to the Juhe news service with the provided parameters (type, page, page_size) and returns the news list as TextContent or an error message.
    async def get_news_list(type: str = "top", page: int = 1, page_size: int = 20) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        """
        根据新闻类型获取今日热点新闻头条.
        """
        url = f"{JUHE_NEWS_API_BASE}/index"
        params = {
            "type": type,
            "page": page,
            "page_size": page_size,
            "key": JUHE_NEWS_API_KEY
        }
        async with httpx.AsyncClient() as client:
            response = await client.get(url, params=params)
            data = response.json()
            if data["error_code"] == 0:
                news_list = data["result"]["data"]
                return [
                    types.TextContent(
                        type="text",
                        text=f"{news_list}"
                    )
                ]
            else:
                return [
                    types.TextContent(
                        type="text",
                        text=f"Error: {data['reason']}"
                    )
                ]
  • Defines the input JSON schema for the 'get_news_list' tool, specifying properties for 'type', 'page', and 'page_size'.
    inputSchema={
        "type": "object",
        "properties": {
            "type": {
                "type": "string", "description": "新闻类型:top(推荐,默认),guonei(国内),guoji(国际),yule(娱乐),tiyu(体育),junshi(军事),keji(科技),caijing(财经),youxi(游戏),qiche(汽车),jiankang(健康)",
            },
            "page": {
                "type": "number", "description": "当前页数, 默认1, 最大50"
            },
            "page_size": {
                "type": "number", "description": "每页返回新闻条数, 默认20, 最大50"
            },
        },
        # "required": ["type"],
    },
  • Registers the 'get_news_list' tool with the MCP server via the list_tools handler, including its name, description, and schema.
    types.Tool(
        name="get_news_list",
        description="通过新闻类型获取今日热点新闻头条",
        inputSchema={
            "type": "object",
            "properties": {
                "type": {
                    "type": "string", "description": "新闻类型:top(推荐,默认),guonei(国内),guoji(国际),yule(娱乐),tiyu(体育),junshi(军事),keji(科技),caijing(财经),youxi(游戏),qiche(汽车),jiankang(健康)",
                },
                "page": {
                    "type": "number", "description": "当前页数, 默认1, 最大50"
                },
                "page_size": {
                    "type": "number", "description": "每页返回新闻条数, 默认20, 最大50"
                },
            },
            # "required": ["type"],
        },
    ),
  • Dispatches calls to the 'get_news_list' tool handler within the call_tool function, extracting the 'type' parameter and invoking the handler.
    if name == "get_news_list":
        type_value = type_value = arguments.get("type", "top") if arguments else "top"
        return await get_news_list(type_value)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool fetches '今日热点新闻头条' (today's hot news headlines), implying a read-only operation that returns current data. However, it lacks details on response format, pagination behavior, error handling, or any limitations like rate limits or data freshness. For a tool with no annotation coverage, this is a significant gap in transparency.

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, efficient sentence: '通过新闻类型获取今日热点新闻头条'. It front-loads the core purpose without unnecessary words, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's function, with zero waste.

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?

Given the tool's complexity (a read operation with 3 parameters and no output schema), the description is incomplete. It lacks details on what the output looks like (e.g., list structure, fields in news items), error conditions, or behavioral traits like pagination limits. Without annotations or an output schema, the description should provide more context to help an agent use the tool effectively.

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 input schema has 100% description coverage, with clear documentation for all three parameters (type, page, page_size), including default values and constraints. The description adds no additional parameter semantics beyond what's in the schema, such as explaining the significance of news types or pagination behavior. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 clearly states the tool's purpose: '通过新闻类型获取今日热点新闻头条' (Get today's hot news headlines by news type). It specifies the verb '获取' (get) and resource '今日热点新闻头条' (today's hot news headlines), making the action and target clear. However, it doesn't explicitly differentiate from its sibling tool 'get_news_content', which likely retrieves full article content rather than headlines.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'get_news_content' or explain scenarios where one would prefer headlines over full content. There's also no information about prerequisites, such as authentication or rate limits, which could affect usage decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juhemcp/jnews-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server