Skip to main content
Glama
team-tissis

NoLang MCP Server

by team-tissis

list_video_settings

Retrieve paginated video configuration options from the NoLang MCP Server to customize AI-generated video creation parameters.

Instructions

Return a paginated list of your VideoSettings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number
has_nextYesTrue if there is another page of results
settingsYesList of video setting summaries
total_settingsYesTotal number of video settings

Implementation Reference

  • The main handler function for the 'list_video_settings' MCP tool. It is decorated with @mcp.tool for registration, calls the NoLang API via nolang_api.list_video_settings, processes the response into VideoSettingSummary objects, and returns a ListVideoSettingsResult.
    @mcp.tool(
        name="list_video_settings",
        description="Return a paginated list of your VideoSettings.",
    )
    async def list_video_settings(args: ListVideoSettingsArgs) -> ListVideoSettingsResult:
        try:
            response = await nolang_api.list_video_settings(args.page)
            summaries = [
                VideoSettingSummary(
                    video_setting_id=s.video_setting_id,
                    title=s.title,
                    updated_at=s.updated_at,
                    required_fields=s.request_fields if isinstance(s.request_fields, dict) else {},
                )
                for s in response.results
            ]
            return ListVideoSettingsResult(
                total_settings=response.total_count,
                page=args.page,
                has_next=response.has_next,
                settings=summaries,
            )
        except httpx.HTTPStatusError as e:
            raise RuntimeError(format_http_error(e)) from e
  • Pydantic schema for the input arguments of the list_video_settings tool, defining the 'page' parameter.
    class ListVideoSettingsArgs(BaseModel):
        """Arguments for listing video settings."""
    
        model_config = ConfigDict(extra="forbid")
    
        page: int = Field(default=1, description="Page number to retrieve", ge=1)
  • Pydantic schema for the output result of the list_video_settings tool.
    class ListVideoSettingsResult(BaseModel):
        model_config = ConfigDict(extra="allow")
    
        total_settings: int = Field(..., description="Total number of video settings")
        page: int = Field(..., description="Current page number")
        has_next: bool = Field(..., description="True if there is another page of results")
        settings: List[VideoSettingSummary] = Field(..., description="List of video setting summaries")
  • Helper method in the NoLangAPI client class that performs the HTTP GET request to retrieve paginated video settings from the API and parses it into VideoSettingsResponse.
    async def list_video_settings(self, page: int = 1) -> VideoSettingsResponse:
        response_data = await self._get("/unstable/video-settings/", params={"page": page})
        return VideoSettingsResponse(**response_data)
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 pagination which is useful, but doesn't describe authentication requirements, rate limits, error conditions, or what happens when no VideoSettings exist. For a listing tool with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness4/5

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

The description is a single, efficient sentence that states the core functionality. It's appropriately sized for a simple listing tool and front-loads the essential information. There's no wasted verbiage or unnecessary elaboration.

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 this is a simple listing tool with 1 parameter and an output schema exists (so return values are documented elsewhere), the description is minimally adequate. However, with no annotations and 0% schema description coverage, it should provide more context about authentication, error handling, and what VideoSettings represent to be truly complete.

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 0%, so the schema provides no parameter documentation. The description mentions 'paginated list' which implies the page parameter exists, but doesn't explain the parameter's purpose, format, or constraints. This adds minimal value beyond what can be inferred from the tool name and schema structure.

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

Purpose3/5

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

The description states the tool returns a paginated list of VideoSettings, which is a clear verb+resource combination. However, it doesn't distinguish this from sibling tools like 'list_generated_videos' - both list operations but for different resources. The purpose is understandable 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. There's no mention of prerequisites, when this tool is appropriate versus other listing tools, or any context about what VideoSettings are. The agent must 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/team-tissis/nolang-mcp'

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