Skip to main content
Glama
Roland0511

MCP Feishu Project Manager

by Roland0511

get_view_detail

Retrieve work item lists from Feishu project management views by specifying a view ID, with pagination support for managing large datasets.

Instructions

根据视图id获取指定视图下的工作项列表 Args: view_id: 视图标识id page_num: 页码,默认为1 page_size: 每页数量,默认为20

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_idYes
page_numNo
page_sizeNo

Implementation Reference

  • MCP tool handler function for 'get_view_detail' that handles authentication and delegates to FSProjClient.get_view_detail. Includes input schema via type hints and docstring.
    @mcp.tool("get_view_detail")
    def get_view_detail(view_id: str, page_num: int = 1, page_size: int = 20):
        """根据视图id获取指定视图下的工作项列表
        Args:
            view_id: 视图标识id
            page_num: 页码,默认为1
            page_size: 每页数量,默认为20
        """
        client.get_plugin_token()
        return client.get_view_detail(view_id, page_num, page_size)
  • Core implementation of get_view_detail in FSProjClient class, performing the actual API GET request to retrieve view details with pagination.
    def get_view_detail(self, view_id: str, page_num: int = 1, page_size: int = 20) -> Dict:
        """获取视图工作项列表
        
        Args:
            view_id: 视图标识
            page_num: 页码
            page_size: 每页数量
            
        """
        
        data = {
            "page_num": page_num,
            "page_size": page_size
        }
        response = self._request(
            "GET", 
            f"/open_api/{self.project_key}/fix_view/{view_id}", 
            params=data
        )
        err_code = response.get("code", 0)
        if err_code != 0:
            raise Exception(f"获取视图工作项列表失败,错误码: {err_code}, 错误信息: {response.get('err_msg')}")
        return response.get("data", {})
  • Registration of the 'get_view_detail' tool using FastMCP decorator.
    @mcp.tool("get_view_detail")
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 (page_num and page_size with defaults), which is useful context beyond just listing parameters. However, it doesn't describe important behavioral aspects like whether this is a read-only operation, what permissions might be required, rate limits, error conditions, or the format/structure of the returned work item list. For a tool with 3 parameters and no annotations, this leaves significant gaps.

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 concise with a clear purpose statement followed by parameter explanations. The two-sentence structure is efficient with zero waste. However, the parameter explanations could be slightly more integrated with the purpose statement rather than presented as a separate 'Args:' section, preventing a perfect score.

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 moderate complexity (3 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose and parameter semantics adequately but lacks behavioral context and usage guidelines. Without annotations or output schema, the description should ideally provide more information about what the tool returns and how it behaves, but it does the minimum viable job for a read operation.

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 description provides meaningful semantic information for all 3 parameters beyond what the schema offers. The schema has 0% description coverage (only titles), while the description explains: 'view_id: 视图标识id' (view identification ID), 'page_num: 页码,默认为1' (page number, default 1), and 'page_size: 每页数量,默认为20' (items per page, default 20). This adds crucial context about parameter purposes and default values that the schema lacks.

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: '根据视图id获取指定视图下的工作项列表' (Get work item list under specified view based on view ID). It specifies the verb '获取' (get) and resource '工作项列表' (work item list) with the scope '指定视图下' (under specified view). However, it doesn't explicitly differentiate from sibling tools like get_view_list or get_work_item_detail, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like get_view_list (which might list views rather than items within a view) or get_view_detail_by_name (which appears to do similar functionality by name instead of ID). There's no context about prerequisites, when this tool is appropriate, or what alternatives exist.

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