Skip to main content
Glama
EfrainTorres

ArmaVita Meta Ads MCP

create_ad

Create and configure Meta ads by specifying ad account, name, ad set, creative, and settings like bid amount and tracking specifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_account_idYes
nameYes
ad_set_idYes
ad_creative_idYes
statusNoPAUSED
bid_amountNo
tracking_specsNo
meta_access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'create_ad' tool is implemented as an async function in 'src/armavita_meta_ads_mcp/core/ad_tools.py'. It takes several arguments like 'ad_account_id', 'name', 'ad_set_id', and 'ad_creative_id', validates them, constructs a payload, and sends a POST request to the Meta Graph API to create the ad.
    async def create_ad(
        ad_account_id: str,
        name: str,
        ad_set_id: str,
        ad_creative_id: str,
        status: str = "PAUSED",
        bid_amount: Optional[int] = None,
        tracking_specs: Optional[List[Dict[str, Any]]] = None,
        meta_access_token: Optional[str] = None,
    ) -> str:
        if not ad_account_id:
            return _json({"error": "No account ID provided"})
        if not name:
            return _json({"error": "No ad name provided"})
        if not ad_set_id:
            return _json({"error": "No ad set ID provided"})
        if not ad_creative_id:
            return _json({"error": "No creative ID provided"})
    
        payload: Dict[str, Any] = {
            "name": name,
            "ad_set_id": ad_set_id,
            "creative": {"ad_creative_id": ad_creative_id},
            "status": status,
        }
        if bid_amount is not None:
            payload["bid_amount"] = str(bid_amount)
    
        encoded_tracking = _build_tracking_specs(tracking_specs)
        if encoded_tracking is not None:
            payload["tracking_specs"] = encoded_tracking
    
        result = await make_api_request(f"{ad_account_id}/ads", meta_access_token, payload, method="POST")
        return _json(result)
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/EfrainTorres/armavita-meta-ads-mcp'

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