Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_ivods

Retrieve IVOD video listings from Taiwan's Legislative Yuan by filtering parameters like term, session, date, committee, or member to access legislative meeting recordings.

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
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the return format (JSON string) and error handling (Chinese error messages), which is helpful. However, it doesn't mention pagination behavior beyond parameter defaults, rate limits, authentication needs, or whether this is a read-only operation. The description adds some context but leaves gaps for a tool with 11 parameters.

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 structured with clear sections (Args, Returns, Raises), but it's verbose due to repeating all parameter details that are already in the schema. The first sentence states the purpose, but the bulk of the text duplicates schema information without adding value. It could be more concise by omitting the parameter list and focusing on usage context.

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 (11 parameters, no annotations, but with output schema), the description is partially complete. It explains the return format and errors, which compensates for missing annotations, but lacks guidance on tool selection versus siblings. The output schema exists, so the description doesn't need to detail return values, but overall completeness is adequate with noticeable gaps in usage guidelines.

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 11 parameters with descriptions and examples. The description repeats this parameter information verbatim in the 'Args' section, adding no additional meaning beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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(網路電視)影片列表' (List IVOD (internet TV) video lists). It specifies the resource (IVOD videos) and action (list), but doesn't differentiate from sibling tools like 'get_ivod' or 'get_meet_ivods', which appear to be related IVOD tools. The purpose is clear but lacks sibling differentiation.

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_ivod' (which might retrieve a single IVOD) or 'get_meet_ivods' (which might list IVODs for a specific meeting), nor does it specify prerequisites or exclusions. Usage context is implied through parameters but not explicitly stated.

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