Skip to main content
Glama
ascentkorea

Hubble MCP Server

by ascentkorea

get_search_path

Retrieve search path analysis results for a keyword from Hubble Path Finder API. Specify region (kr or jp) and result limit.

Instructions

Make a request to the Path Finder API of Hubble with proper error handling. Args: keyword: str, 검색 키워드(모든 키워드는 소문자로 변환하여 요청) gl: str, 지역 코드 한국 일본(kr, jp) limit: int, 검색 경로 분석 결과 최대 개수(기본값 300) Returns: dict[str, Any] | None: 검색 키워드의 검색 경로 분석 결과

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes
glNokr
limitNo

Implementation Reference

  • data_api.py:280-283 (registration)
    Tool registration via @mcp.tool() decorator on FastMCP instance
    mcp = FastMCP("hubble")
    @mcp.tool()
    @async_retry(exceptions=(Exception), tries=2, delay=0.3)
    async def get_search_path(keyword: str,
  • Input schema: keyword (str), gl (Literal['kr','jp']), limit (int=300), returns dict or None
    async def get_search_path(keyword: str,
                              gl: Literal['kr', 'jp'] = "kr",
                              limit=300) -> dict[str, Any] | None:
        """Make a request to the Path Finder API of Hubble with proper error handling.
            Args:
                keyword: str, 검색 키워드(모든 키워드는 소문자로 변환하여 요청)
                gl: str, 지역 코드 한국 일본(kr, jp)
                limit: int, 검색 경로 분석 결과 최대 개수(기본값 300)
            Returns:
                dict[str, Any] | None: 검색 키워드의 검색 경로 분석 결과
        """
  • Handler: Sends POST request to Hubble Path Finder API with keyword, gl, limit; returns response text
    async def get_search_path(keyword: str,
                              gl: Literal['kr', 'jp'] = "kr",
                              limit=300) -> dict[str, Any] | None:
        """Make a request to the Path Finder API of Hubble with proper error handling.
            Args:
                keyword: str, 검색 키워드(모든 키워드는 소문자로 변환하여 요청)
                gl: str, 지역 코드 한국 일본(kr, jp)
                limit: int, 검색 경로 분석 결과 최대 개수(기본값 300)
            Returns:
                dict[str, Any] | None: 검색 키워드의 검색 경로 분석 결과
        """
        payload = {"keyword": keyword, "gl": gl, "limit": limit}
        headers = {"X-API-Key": HUBBLE_API_KEY}
        async with httpx.AsyncClient() as client:
            response = await client.post(
                f"{HUBBLE_API_URL}/path_finder",
                headers=headers,
                json=payload,
                timeout=30.0)
            response.raise_for_status()
            return response.text
Behavior2/5

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

With no annotations, the description should fully disclose behavioral traits. It mentions lowercase conversion and error handling, but omits side effects, authentication, rate limits, and mutation status. The 'dict or None' return type is stated but no details on failure modes.

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 uses a docstring format ('Args:', 'Returns:') which is not ideal for MCP. It is moderately concise but front-loads an irrelevant implementation detail ('proper error handling') instead of the core purpose.

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

Completeness3/5

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

Given no output schema and no annotations, the description explains the core behavior and return type but lacks details on return structure, error scenarios, constraints, and potential side effects. It partially completes the picture.

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

Parameters4/5

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

Schema coverage is 0%, so the description is crucial. It provides type, role, and default for all three parameters (keyword lowercase, gl enum, limit as int with default 300), adding significant value beyond the schema types.

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 the tool makes a request to the Path Finder API and returns search path analysis results, which is clear but not a concise verb+resource. It distinguishes from siblings (crawl_* tools) but could be more specific.

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 explicit guidance on when to use this tool versus alternatives. Sibling tools (crawl_*, get_graph_info, get_keyword_info) are not referenced for comparison, leaving the agent to infer usage.

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