Skip to main content
Glama

get_recently_updated_defect_list

Retrieve recently updated defect lists from Feishu by specifying status and date range to monitor and manage development issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
startDateYes
endDateYes

Implementation Reference

  • Registration of the 'get_recently_updated_defect_list' tool, including Zod input schema for status, startDate, endDate and the inline async handler that fetches records via feishuService and returns JSON-formatted response.
      "get_recently_updated_defect_list",
      {
        status: z.string(),
        startDate: z.number(),
        endDate: z.number(),
      },
      async ({ status, startDate, endDate }) => {
        const records = await feishuService.getRecordsByStatus(status, startDate, endDate);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ records }, null, 2) 
          }]
        };
      }
    );
  • Core implementation in FeishuService.getRecordsByStatus: authenticates with Feishu, constructs a search query filter for status and recent update time range, sorts by update time descending, and returns the matching records.
    async getRecordsByStatus(status: string, startDate: number, endDate: number): Promise<any[]> {
      const tenantAccessToken = await this.getTenantAccessToken();
      // 构造请求体
      const requestBody = {
        filter: {
          conjunction: "and",
          conditions: [
            {
              field_name: "状态",
              operator: "is",
              value: [status], // 筛选状态字段为指定值(如“已修复”)
            },
            {
              field_name: "最近更新时间",
              operator: "isGreaterEqual",
              value: [startDate], // 开始日期
            },
            {
              field_name: "最近更新时间",
              operator: "isLessEqual",
              value: [endDate], // 结束日期
            },
          ],
        },
        sort: [
          {
            field_name: "最近更新时间",
            desc: true, // 按最近更新时间倒序排序
          },
        ],
        field_names: ["状态", "最近更新时间"], // 返回字段
      };
      // 调用查询记录 API
      const { data } = await axios.post(
        `https://open.feishu.cn/open-apis/bitable/v1/apps/${this.APP_TOKEN}/tables/${this.TABLE_ID}/records/search`,
        requestBody,
        {
          headers: {
            Authorization: `Bearer ${tenantAccessToken}`,
            "Content-Type": "application/json",
          },
        }
      );
      if (data.code !== 0) {
        throw new Error(`Failed to get records: ${data.msg}`);
      }
      return data.data.items; // 返回记录列表
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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