Skip to main content
Glama
JanNafta

PropellerAds MCP Server

by JanNafta

get_available_countries

Retrieve the list of countries available for ad targeting to ensure campaigns reach the correct geographic audiences.

Instructions

Get list of available countries for targeting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The underlying client method that performs the API request to fetch countries.
    def get_countries(self) -> list[dict[str, Any]]:
        """Get available countries for targeting."""
        result = self._request("GET", "/adv/countries")
        return result.get("data", result) if isinstance(result, dict) else result
  • The handler in the server logic that executes the tool and formats the output.
    elif name == "get_available_countries":
        countries = client.get_countries()
        return f"# Available Countries\n\n```json\n{json.dumps(countries, indent=2)}\n```"
  • Registration of the get_available_countries tool in the server.
        name="get_available_countries",
        description="Get list of available countries for targeting.",
        inputSchema={"type": "object", "properties": {}},
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a list, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data (e.g., with country codes or names), or if the list is static or dynamic. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, clear sentence: 'Get list of available countries for targeting.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool with no parameters. Every part of the sentence earns its place by specifying the action and resource.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavioral aspects like return format or usage context. Without annotations or output schema, the description should ideally provide more context (e.g., what 'available' means or how the list is used), but it's not entirely incomplete for a basic retrieval tool.

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 0 parameters with 100% coverage, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline of 4 for this dimension, as it doesn't have to compensate for any gaps in schema documentation.

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: 'Get list of available countries for targeting.' It specifies the verb ('Get') and resource ('list of available countries'), making it easy to understand what the tool does. However, it doesn't distinguish itself from potential sibling tools that might also retrieve country-related data, such as if there were a 'get_targetable_countries' tool.

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 prerequisites, context (e.g., for campaign setup or targeting configuration), or exclusions. Given the sibling tools include campaign-related operations like 'create_campaign' and 'update_campaign', it's unclear if this tool is used independently or as part of those workflows.

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/JanNafta/propellerads-mcp'

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