Skip to main content
Glama
AceDataCloud

SerpMCP

by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

serp_list_countries

Get a table of country codes to localize Google search results for targeted country-specific queries.

Instructions

List commonly used country codes for Google search.

Shows common country codes that can be used to localize search results.

Returns:
    Table of country codes and their countries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • tools/info_tools.py:38-64 (handler)
    The main handler function for the serp_list_countries tool. It is decorated with @mcp.tool() which registers it as an MCP tool. Returns a formatted markdown table listing common country codes for Google search localization.
    async def serp_list_countries() -> str:
    """List commonly used country codes for Google search.

    Shows common country codes that can be used to localize search results.

    Returns:
        Table of country codes and their countries.
    """
    # Last updated: 2026-04-05
    return """Common Country Codes for Google Search:

| Code | Country           | Code | Country           |
|------|-------------------|------|-------------------|
| us   | United States     | jp   | Japan             |
| uk   | United Kingdom    | kr   | South Korea       |
| cn   | China             | in   | India             |
| de   | Germany           | br   | Brazil            |
| fr   | France            | mx   | Mexico            |
| es   | Spain             | it   | Italy             |
| ca   | Canada            | au   | Australia         |
| ru   | Russia            | nl   | Netherlands       |
| sg   | Singapore         | hk   | Hong Kong         |
| tw   | Taiwan            | th   | Thailand          |

Usage: Pass the country code to the `country` parameter.
Example: serp_google_search(query="news", country="uk")
"""
  • main.py:179-181 (registration)
    Explicit registration of the serp_list_countries tool name and description in the server card endpoint (line 180).
    {
    "name": "serp_list_countries",
    "description": "List supported countries",
  • main.py:125-125 (registration)
    The tool name is printed in the startup banner listing available tools.
    safe_print("    - serp_list_countries")
  • tools/info_tools.py:38-39 (schema)
    The tool's signature defines no input parameters and returns a string, serving as its type schema.
    async def serp_list_countries() -> str:
    """List commonly used country codes for Google search.

Tool Definition Quality

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention whether the list is exhaustive, static or dynamic, or if any rate limits or return size constraints apply. The phrase 'commonly used' is ambiguous, leaving important traits undisclosed.

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 three sentences long, front-loading the purpose. It is efficient but the first sentence could be merged with the second. Overall, it conveys necessary information without verbosity.

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 has no parameters and an output schema exists (as indicated), the description provides a minimal but adequate outline. However, it does not explain what 'commonly used' implies or offer usage examples, which slightly reduces completeness for a first-time user.

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

Parameters4/5

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

The input schema has zero parameters, so schema coverage is 100% automatically. The description adds no parameter details, which is acceptable given no parameters exist. Baseline for zero parameters is 4, and the description does not detract from that.

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 explicitly states the tool lists 'commonly used country codes for Google search'. It clearly identifies the verb (list) and resource (country codes), and distinguishes itself from sibling tools like serp_list_languages by specifying the domain (Google search localization).

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?

The description implies usage for localizing search results ('can be used to localize search results'), but does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools. The context is clear but lacks exclusions.

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