Skip to main content
Glama
qiniu

Qiniu MCP Server

Official
by qiniu

live_streaming_list_buckets

Retrieve a list of all available live streaming spaces or buckets to manage and organize your streaming content on Qiniu Cloud.

Instructions

List all live streaming spaces/buckets. Returns information about all available live streaming buckets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'live_streaming_list_buckets' that delegates to the LiveStreamingService.list_buckets method.
    async def list_buckets(self, **kwargs) -> list[types.TextContent]:
        result = await self.live_streaming.list_buckets(**kwargs)
        return [types.TextContent(type="text", text=str(result))]
  • Input schema definition for the 'live_streaming_list_buckets' tool, which requires no parameters.
    types.Tool(
        name="live_streaming_list_buckets",
        description="List all live streaming spaces/buckets. Returns information about all available live streaming buckets.",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": [],
        },
    )
  • Tool registration function that registers the 'list_buckets' handler along with other live streaming tools.
    def register_tools(live_streaming: LiveStreamingService):
        tool_impl = _ToolImpl(live_streaming)
        tools.auto_register_tools(
            [
                tool_impl.create_bucket,
                tool_impl.create_stream,
                tool_impl.bind_push_domain,
                tool_impl.bind_play_domain,
                tool_impl.get_push_urls,
                tool_impl.get_play_urls,
                tool_impl.query_live_traffic_stats,
                tool_impl.list_buckets,
                tool_impl.list_streams,
            ]
        )
  • Core helper method in LiveStreamingService that implements the bucket listing logic by making an authenticated GET request to the live streaming API endpoint.
    async def list_buckets(self) -> Dict[str, Any]:
        """
        List all live streaming spaces/buckets
    
        Returns:
            Dict containing the list of buckets
        """
        if not self.live_endpoint:
            self.live_endpoint = "mls.cn-east-1.qiniumiku.com"
    
        # Remove protocol to get base endpoint
        endpoint = self.live_endpoint
        if endpoint.startswith("http://"):
            endpoint = endpoint[7:]
        elif endpoint.startswith("https://"):
            endpoint = endpoint[8:]
    
        url = f"https://{endpoint}/"
        headers = self._get_auth_header(method="GET", url=url)
    
        logger.info(f"Listing all live streaming buckets from {url}")
    
        async with aiohttp.ClientSession() as session:
            async with session.get(url, headers=headers) as response:
                status = response.status
                text = await response.text()
    
                if status == 200:
                    logger.info("Successfully listed all buckets")
                    return {
                        "status": "success",
                        "data": text,
                        "message": "Buckets listed successfully",
                        "status_code": status
                    }
                else:
                    logger.error(f"Failed to list buckets, status: {status}, response: {text}")
                    return {
                        "status": "error",
                        "message": f"Failed to list buckets: {text}",
                        "status_code": status
                    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Returns information about all available live streaming buckets' which hints at read-only behavior, but doesn't specify what information is returned, whether there's pagination, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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 perfectly concise with two clear sentences that directly state the tool's function and return value. Every word earns its place with no redundancy or unnecessary elaboration. It's appropriately sized for a simple listing tool.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does and what it returns, but lacks details about the return format, error handling, or operational constraints. For a listing tool without annotations, more context about the response structure would be helpful.

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?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it correctly doesn't mention any. No additional parameter semantics are needed or provided.

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: 'List all live streaming spaces/buckets' with the verb 'List' and resource 'live streaming spaces/buckets'. It distinguishes from generic 'list_buckets' by specifying 'live streaming' scope, though it doesn't explicitly differentiate from 'live_streaming_list_streams' which lists streams rather than buckets.

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. It doesn't mention when to choose this over 'list_buckets' (for general storage) or 'live_streaming_list_streams' (for streams within buckets). The description only states what it does, not when it's appropriate.

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/qiniu/qiniu-mcp-server'

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