Skip to main content
Glama
Alex-Smith-1234

讯飞智文PPT生成服务MCP Server

get_theme_list

Retrieve available PowerPoint templates by filtering style, color, industry, and payment type to obtain template IDs for presentation generation.

Instructions

获取PPT模板列表。

使用说明:
1. 此工具用于获取可用的PPT模板列表,需先调用本工具获取template_id,后续PPT生成需用到。
2. 可通过style、color、industry等参数筛选模板。
3. 需先设置环境变量AIPPT_APP_ID和AIPPT_API_SECRET。

参数:
- pay_type: 模板付费类型,可选值:free-免费模板,not_free-付费模板。
- style: 模板风格,如:简约、商务、科技等。
- color: 模板颜色,如:红色、蓝色等。
- industry: 模板行业,如:教育培训、金融等。
- page_num: 页码,从1开始。
- page_size: 每页数量,最大100。

返回:
包含模板列表的字典,每个模板包含template_id等信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pay_typeNonot_free
styleNo
colorNo
industryNo
page_numNo
page_sizeNo

Implementation Reference

  • The main handler function for the 'get_theme_list' tool, decorated with @mcp.tool() for automatic registration in FastMCP. It retrieves PPT template lists from the iFlytek API using specified filters and pagination, returning the raw JSON response.
    @mcp.tool()
    def get_theme_list(
        ctx: Context,
        pay_type: str = "not_free",
        style: Optional[str] = None,
        color: Optional[str] = None,
        industry: Optional[str] = None,
        page_num: int = 2,
        page_size: int = 10
    ) -> Dict[str, Any]:
        """
        获取PPT模板列表。
        
        使用说明:
        1. 此工具用于获取可用的PPT模板列表,需先调用本工具获取template_id,后续PPT生成需用到。
        2. 可通过style、color、industry等参数筛选模板。
        3. 需先设置环境变量AIPPT_APP_ID和AIPPT_API_SECRET。
        
        参数:
        - pay_type: 模板付费类型,可选值:free-免费模板,not_free-付费模板。
        - style: 模板风格,如:简约、商务、科技等。
        - color: 模板颜色,如:红色、蓝色等。
        - industry: 模板行业,如:教育培训、金融等。
        - page_num: 页码,从1开始。
        - page_size: 每页数量,最大100。
        
        返回:
        包含模板列表的字典,每个模板包含template_id等信息。
        """
        url = "https://zwapi.xfyun.cn/api/ppt/v2/template/list"
        headers = get_headers()
        params = {
            "payType": pay_type,
            "pageNum": page_num,
            "pageSize": page_size
        }
        if style:
            params["style"] = style
        if color:
            params["color"] = color
        if industry:
            params["industry"] = industry
        response = requests.get(url, headers=headers, params=params)
    
        if response.status_code != 200:
            raise Exception(f"调用失败: {response.text}")
    
        return response.text
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does reveal that this is a read operation (获取/获取), mentions pagination behavior (page_num, page_size with max 100), and notes authentication prerequisites. However, it doesn't disclose rate limits, error conditions, or whether the operation is idempotent/cacheable.

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 well-structured with clear sections (purpose, usage instructions, parameters, return). Most sentences earn their place, though the Chinese formatting with numbered lists and bullet points is slightly verbose. The core information is front-loaded appropriately.

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

Completeness4/5

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

For a 6-parameter read operation with no annotations and no output schema, the description does quite well. It covers purpose, prerequisites, all parameters, pagination behavior, and return format. The main gap is lack of output schema details (only mentions '包含模板列表的字典' - contains template list dictionary), but given the context, this is reasonably complete.

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

Parameters5/5

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

The schema has 0% description coverage, so the description must fully compensate. It provides excellent parameter semantics: it explains all 6 parameters with clear meanings, optional values for pay_type, examples for style/color/industry, and constraints for page_size. This adds substantial value beyond the bare schema.

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

Purpose5/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 as '获取PPT模板列表' (get PPT template list), which is a specific verb+resource combination. It distinguishes this tool from its siblings (create_outline, create_ppt_by_outline, etc.) by focusing on template retrieval rather than creation or task management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: it explains that this tool should be called first to obtain template_id for subsequent PPT generation. It also mentions environment variable prerequisites (AIPPT_APP_ID and AIPPT_API_SECRET). However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among siblings.

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/Alex-Smith-1234/zwppt-mcp'

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