Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_meet_ivods

Retrieve IVOD video listings for specific Legislative Yuan meetings by providing meeting identifiers like meet_id, date, or committee code to access parliamentary proceedings recordings.

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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return format (JSON) and error handling (Chinese error messages), but lacks critical information about whether this is a read-only operation, rate limits, authentication requirements, or pagination behavior beyond the page/limit parameters. For a tool with 12 parameters and no annotations, this is insufficient behavioral context.

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 reasonably structured with purpose statement, Args, Returns, and Raises sections. However, it's verbose with redundant parameter documentation that duplicates the schema. The Args section adds no value since schema coverage is 100%. The description could be more concise by focusing only on what the schema doesn't cover.

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 complexity (12 parameters, 1 required) and the existence of an output schema (implied by 'Returns: str: JSON格式'), the description is minimally adequate. It states the purpose and return format, but lacks behavioral context and usage guidance. With no annotations and multiple sibling tools, the description should do more to help an agent understand when and how to use this tool effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description repeats parameter information in the Args section, adding no meaningful semantic value beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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: '取得特定會議相關的 IVOD(網路電視)影片列表' (Get IVOD video list for specific meetings). It specifies the verb ('取得' - get) and resource ('IVOD影片列表' - IVOD video list), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_ivod' or 'list_ivods', which appear to be related IVOD tools.

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. With sibling tools like 'get_ivod' and 'list_ivods' available, there's no indication of how this tool differs or when it should be preferred. The description only states what the tool does, not when to use it.

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