Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_meet_ivods

Retrieve IVOD video list for a specific meeting using meeting code, date, or committee; supports pagination and custom fields.

Instructions

取得特定會議相關的 IVOD(網路電視)影片列表。

Args:
    meet_id: 會議代碼,必填,例:院會-11-2-3
    term: 屆,例:11
    session: 會期,例:2
    meeting_code: 會議代碼,例:委員會-11-2-22-5
    member_name: 委員名稱,例:陳培瑜
    committee_code: 委員會代碼,例:22
    meeting_code_data: 會議資料.會議代碼,例:委員會-11-2-22-5
    date: 日期,格式:YYYY-MM-DD,例:2024-10-24
    video_type: 影片種類,Clip(片段)或 Full(完整)
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式,包含會議相關的 IVOD 影片列表資料。

Raises:
    例外時回傳中文錯誤訊息字串。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meet_idYes會議代碼,必填,例:院會-11-2-3
termNo屆,例:11
sessionNo會期,例:2
meeting_codeNo會議代碼,例:委員會-11-2-22-5
member_nameNo委員名稱,例:陳培瑜
committee_codeNo委員會代碼,例:22
meeting_code_dataNo會議資料.會議代碼,例:委員會-11-2-22-5
dateNo日期,格式:YYYY-MM-DD,例:2024-10-24
video_typeNo影片種類,Clip(片段)或 Full(完整)
pageNo頁數,預設1
limitNo每頁筆數,預設20,建議不超過100
output_fieldsNo自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states that the return is a JSON string and raises errors with Chinese messages. There is no mention of read-only nature, idempotency, authentication requirements, rate limits, or any side effects.

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

Conciseness3/5

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

The description is well-structured with Args, Returns, and Raises sections. However, it redundantly lists all parameter descriptions that are already in the schema, making it longer than necessary. It is front-loaded with the purpose statement but could be more concise.

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

Completeness2/5

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

Given the tool has 12 parameters (1 required) and an output schema exists, the description should guide on how to use the many optional filters effectively. It lacks information on typical combinations, error handling beyond a generic statement, and does not clarify the relationship between similar parameters (e.g., meet_id vs meeting_code_data).

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

Parameters2/5

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

Schema coverage is 100% (every parameter has a description), so baseline is 3. However, the description repeats the schema descriptions verbatim without adding new meaning (e.g., the difference between 'meeting_code' and 'meeting_code_data'). It provides no extra syntactic or semantic value beyond the schema.

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 that the tool retrieves the list of IVOD videos related to a specific meeting, distinguishing it from siblings like 'list_ivods' (likely general listing) and 'get_ivod' (single video). The verb '取得' (retrieve) and resource '特定會議相關的 IVOD 影片列表' are specific.

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, no prerequisites, and no explanation of which optional filter parameters are recommended. It simply lists parameters without context on their typical usage.

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/narumiruna/ly-mcp'

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