Skip to main content
Glama
ascentkorea

Hubble MCP Server

by ascentkorea

crawl_web_page

Crawl a list of web pages to extract their content and data.

Instructions

웹 페이지 크롤링
args:
    url_list: List[str], 크롤링할 웹 페이지 리스트
returns:
    dict[Any] | None: 크롤링 결과

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
url_listYes

Implementation Reference

  • data_api.py:402-402 (registration)
    The tool is registered via the @mcp.tool() decorator on line 402.
    @mcp.tool()
  • The handler function 'crawl_web_page' that executes the web crawling logic. It accepts a list of URLs, sends a POST request to the HUBBLE_API_URL/web_crawl endpoint with the URLs, and returns the response text.
    async def crawl_web_page(
            url_list: List[str]) -> dict[Any] | None:
        '''
        웹 페이지 크롤링
        args:
            url_list: List[str], 크롤링할 웹 페이지 리스트
        returns:
            dict[Any] | None: 크롤링 결과
        '''
        async with httpx.AsyncClient() as client:
            headers = {"X-API-Key": HUBBLE_API_KEY}
            response = await client.post(
                f"{HUBBLE_API_URL}/web_crawl",
                headers=headers,
                json={"urls": url_list},
                timeout=30.0)
            response.raise_for_status()
            return response.text
  • The @async_retry decorator applied to the handler, providing retry logic (2 tries with 0.3s delay) for transient failures.
    @async_retry(exceptions=(Exception), tries=2, delay=0.3)
  • The async_retry helper function that provides retry logic used by the crawl_web_page tool.
    def async_retry(exceptions=(Exception), tries=3, delay=0.3, logger=None):
        def wrapper(func):
            @wraps(func)
            async def wrapped(*args, **kwargs):
                Tries = []
                for i in range(tries):
                    try:
                        return await func(*args, **kwargs)
                    except exceptions as ex:
                        ex_msg = f"Tries({ex.__class__.__name__}) Cnt: {i+1}, {ex}"
                        Tries.append(ex_msg)
                        if logger:
                            logger.warning(ex_msg)
                        else:
                            print(ex_msg)
                        if delay:
                            await asyncio.sleep(delay)
                raise TooManyTriesException(Tries)
            return wrapped
        return wrapper
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. It only states 'crawl web page' without disclosing error handling, rate limits, authentication needs, or what happens with non-accessible pages. The behavioral profile is completely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and structured with args and returns, but it is overly minimal. It is not wasteful, but it lacks necessary detail. Better structuring with examples or clearer formatting would improve it.

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 that there is no output schema and no annotations, the description is incomplete. The return value is vaguely described as 'dict[Any] | None', leaving the agent unsure about the structure. Critical behavioral aspects like error handling are missing.

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

Parameters2/5

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

The schema has 0% description coverage, and the description adds no meaningful information beyond the schema. It rephrases the parameter as 'list of web pages to crawl' which adds no new constraints or formatting details. The return type is mentioned as 'dict[Any] | None' without further clarification.

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 states 'Crawl web page' which is a clear verb+resource. However, it does not differentiate from sibling tools like crawl_google_serp, which also crawl web pages but with specific Google scope. The generic name implies any URL, but the description fails to explicitly state that.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or when not to use it. The sibling tools (e.g., crawl_google_serp) are not referenced for comparison.

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/ascentkorea/hubble_mcp'

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