Skip to main content
Glama

hz_run_pipeline

Execute a content pipeline to fetch, score, filter, enrich, and summarize data from multiple sources for analysis.

Instructions

一键执行抓取->打分->过滤->富化->摘要。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNo
languagesNo
thresholdNo
horizon_pathNo
config_pathNo
sourcesNo
enrichNo
topic_dedupNo
save_to_horizon_dataNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `hz_run_pipeline` function is defined as an MCP tool handler in `horizon_mcp/server.py`, which delegates the execution to `service.run_pipeline`.
    async def hz_run_pipeline(
        hours: int = 24,
        languages: list[str] | None = None,
        threshold: float | None = None,
        horizon_path: str | None = None,
        config_path: str | None = None,
        sources: list[str] | None = None,
        enrich: bool = True,
        topic_dedup: bool = True,
        save_to_horizon_data: bool = False,
    ) -> dict[str, Any]:
        """一键执行抓取->打分->过滤->富化->摘要。"""
    
        return await _run_tool(
            "hz_run_pipeline",
            lambda: service.run_pipeline(
                hours=hours,
                languages=languages,
                threshold=threshold,
                horizon_path=horizon_path,
                config_path=config_path,
                sources=sources,
                enrich=enrich,
                topic_dedup=topic_dedup,
                save_to_horizon_data=save_to_horizon_data,
            ),
        )
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only lists the pipeline steps without explaining what the tool actually does behaviorally—e.g., whether it's read-only or destructive, its permissions, rate limits, or output format. This is inadequate for a tool with 9 parameters and no annotation coverage.

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?

The description is a single, efficient sentence in Chinese that lists the pipeline steps concisely. It's front-loaded with the core action ('一键执行') and wastes no words, though it could benefit from slightly more detail given the tool's complexity.

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 (9 parameters, no annotations, 0% schema coverage), the description is incomplete. It doesn't explain the tool's behavior, parameter roles, or output (even though an output schema exists, the description doesn't hint at what it returns). For a multi-step pipeline tool, this leaves significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 9 parameters are documented in the schema. The description adds no information about what parameters like 'hours', 'languages', or 'threshold' mean or how they affect the pipeline. It fails to compensate for the lack of schema documentation, leaving parameters entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '一键执行抓取->打分->过滤->富化->摘要' clearly states the tool executes a pipeline of operations (crawl, score, filter, enrich, summarize), which is a specific verb+sequence. However, it doesn't distinguish this from sibling tools like hz_fetch_items, hz_score_items, etc., which handle individual pipeline steps, so the purpose is clear but lacks sibling differentiation.

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 its siblings (e.g., hz_fetch_items for just crawling, hz_score_items for just scoring). It implies usage for a full pipeline execution but doesn't specify contexts, prerequisites, or alternatives, leaving the agent to guess based on tool names alone.

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/henry-insomniac/Horizon-mcp'

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