Skip to main content
Glama
Roland0511

MCP Feishu Project Manager

by Roland0511

get_view_detail_by_name

Retrieve work item lists from Feishu project views by name, filtering by type (story, version, or issue) with pagination controls.

Instructions

根据视图名称获取指定视图下的工作项列表 Args: view_name: 视图名称 work_item_type_key: 工作项类型,可选值为"story"、"version"、"issue", 分别对应需求、版本、缺陷。 page_num: 页码,默认为1 page_size: 每页数量,默认为20

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_nameYes
work_item_type_keyYes
page_numNo
page_sizeNo

Implementation Reference

  • The main handler function for the 'get_view_detail_by_name' tool. It is decorated with @mcp.tool for registration and implements the logic to find a view by name using client.get_view_list and retrieve its details with client.get_view_detail.
    @mcp.tool("get_view_detail_by_name")
    def get_view_detail_by_name(view_name: str, work_item_type_key: WorkItemType, page_num: int = 1, page_size: int = 20):
        """根据视图名称获取指定视图下的工作项列表
        Args:
            view_name: 视图名称
            work_item_type_key: 工作项类型,可选值为"story"、"version"、"issue", 分别对应需求、版本、缺陷。
            page_num: 页码,默认为1
            page_size: 每页数量,默认为20
        """
        client.get_plugin_token()
        # 获取所有视图列表
        view_list = client.get_view_list(work_item_type_key)
        # 查找指定名称的视图
        view = next((v for v in view_list if v["name"] == view_name), None)
        if view:
            # 如果找到视图,获取其ID
            view_id = view["view_id"]
            return client.get_view_detail(view_id, page_num, page_size)
        else:
            return {}
Behavior2/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 mentions pagination behavior (default page_num=1, page_size=20) which is useful, but doesn't cover other important aspects like authentication requirements, rate limits, error conditions, or what happens when the view doesn't exist. For a tool with 4 parameters and no annotation coverage, this is insufficient.

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 appropriately sized and well-structured. It starts with the core purpose, then lists parameters with clear explanations. Each parameter description earns its place by adding value beyond the schema. The formatting with 'Args:' section makes it easy to parse.

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 4 parameters, no annotations, and no output schema, the description does a good job with parameters but lacks completeness. It doesn't explain what the tool returns (work item list format), error conditions, or authentication requirements. For a data retrieval tool with pagination, more behavioral context would be helpful, though the parameter documentation is strong.

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 description provides excellent parameter semantics beyond the input schema. While schema description coverage is 0%, the description explains: 1) view_name is required, 2) work_item_type_key has specific enum values with Chinese translations ('story'='需求', 'version'='版本', 'issue'='缺陷'), 3) page_num defaults to 1, 4) page_size defaults to 20. This fully compensates for the lack of schema descriptions.

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: '根据视图名称获取指定视图下的工作项列表' (Get work item list under specified view by view name). It specifies the verb ('获取' - get) and resource ('工作项列表' - work item list), but doesn't differentiate from sibling tools like 'get_view_detail' or 'get_view_list', which likely have similar functionality.

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 about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'get_view_detail' or 'get_view_list', nor does it explain what distinguishes this tool from them. There's no context about prerequisites or when-not-to-use scenarios.

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/Roland0511/mcp-feishu-proj'

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