Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_ivods

List IVOD video recordings from Taiwan's Legislative Yuan. Filter by committee, legislator, date, or meeting code to find clips or full sessions.

Instructions

列出 IVOD(網路電視)影片列表。

Args:
    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
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, the description carries full burden for behavioral disclosure. It only states the return format (JSON) and error handling (Chinese error messages). It omits important traits like pagination limits, default ordering, read-only nature, or rate limits, which are critical for safe invocation.

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 moderately concise with a clear initial sentence, but the parameter list duplicates the schema information and could be condensed. It is front-loaded with purpose but not optimized for quick scanning.

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?

The tool has 11 filter parameters and an output schema. The description explains what the tool does and provides examples, but misses contextual details like how filters combine (AND/OR) or the default output structure. However, the existence of an output schema partly compensates for missing return information.

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?

The input schema has 100% description coverage, providing examples for all 11 parameters. The tool description repeats these examples but adds no significant additional meaning beyond the schema. Thus, the value added is minimal, warranting the baseline score of 3.

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

Purpose5/5

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

The description clearly states '列出 IVOD 影片列表' (list IVOD video list), specifying the verb (list) and resource (IVOD videos). It distinguishes from sibling tools like get_ivod (single item) and other list tools by focusing on IVOD videos.

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, such as get_ivod or other list tools. It does not mention scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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