Skip to main content
Glama

serp_list_languages

List commonly used Google search language codes to target results in specific languages. Returns a table of language codes and their languages.

Instructions

List commonly used language codes for Google search.

Shows common language codes that can be used to get results in specific languages.

Returns:
    Table of language codes and their languages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the serp_list_languages tool. It is decorated with @mcp.tool() and returns a formatted markdown table of common language codes for Google Search (e.g., en, zh-cn, es).
    @mcp.tool()
    async def serp_list_languages() -> str:
        """List commonly used language codes for Google search.
    
        Shows common language codes that can be used to get results in specific languages.
    
        Returns:
            Table of language codes and their languages.
        """
        # Last updated: 2026-04-05
        return """Common Language Codes for Google Search:
    
    | Code    | Language              | Code    | Language              |
    |---------|----------------------|---------|----------------------|
    | en      | English              | ja      | Japanese             |
    | zh-cn   | Chinese (Simplified) | ko      | Korean               |
    | zh-tw   | Chinese (Traditional)| hi      | Hindi                |
    | es      | Spanish              | pt      | Portuguese           |
    | fr      | French               | ru      | Russian              |
    | de      | German               | ar      | Arabic               |
    | it      | Italian              | th      | Thai                 |
    | nl      | Dutch                | vi      | Vietnamese           |
    | pl      | Polish               | tr      | Turkish              |
    
    Usage: Pass the language code to the `language` parameter.
    Example: serp_google_search(query="news", language="zh-cn")
    """
  • main.py:183-186 (registration)
    Registration entry in the main.py tools list describing the tool for the MCP server manifest (name: serp_list_languages, description: List supported languages).
    {
        "name": "serp_list_languages",
        "description": "List supported languages",
    },
  • main.py:126-126 (registration)
    Registration listing in the startup printout of available tools.
    safe_print("    - serp_list_languages")
  • The @mcp.tool() decorator from FastMCP implicitly handles schema/registration. The function has no parameters, and its return type is str (markdown table).
    @mcp.tool()
    async def serp_list_languages() -> str:
  • The FastMCP server instance (mcp) that powers the @mcp.tool() decorator, defined in core/server.py.
    mcp = FastMCP(
        settings.server_name,
        icons=[Icon(src="", mimeType="image/png")],
        **mcp_kwargs,
    )
Behavior4/5

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

No annotations provided, but description clearly states it returns a table of language codes and languages; limited detail on 'commonly used' subset.

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

Conciseness5/5

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

Three concise sentences, no unnecessary words, front-loaded with purpose.

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

Completeness4/5

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

Sufficient for a simple list tool with output schema; could mention that it returns only commonly used codes.

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

Parameters5/5

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

No parameters exist; schema coverage is 100%, so description adds no parameter info but doesn't need to.

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?

Explicitly states it lists language codes for Google search, differentiating from sibling tools that list countries, search types, or time ranges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for obtaining language codes needed for other tools, but no explicit when-to-use or alternatives guidance.

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/AceDataCloud/SerpMCP'

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