Skip to main content
Glama
EfrainTorres

ArmaVita Meta Ads MCP

update_ad

Modify Meta ad campaign parameters including status, bid amount, creative ID, and tracking specifications to optimize performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYes
statusNo
bid_amountNo
tracking_specsNo
ad_creative_idNo
meta_access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the `update_ad` tool, which updates ad properties like status, bid_amount, tracking_specs, or ad_creative_id via the Meta API.
    async def update_ad(
        ad_id: str,
        status: Optional[str] = None,
        bid_amount: Optional[int] = None,
        tracking_specs: Optional[List[Dict[str, Any]]] = None,
        ad_creative_id: Optional[str] = None,
        meta_access_token: Optional[str] = None,
    ) -> str:
        if not ad_id:
            return _json({"error": "Ad ID is required"})
    
        payload: Dict[str, Any] = {}
        if status is not None:
            payload["status"] = status
        if bid_amount is not None:
            payload["bid_amount"] = str(bid_amount)
        if tracking_specs is not None:
            payload["tracking_specs"] = json.dumps(tracking_specs)
        if ad_creative_id is not None:
            payload["creative"] = json.dumps({"ad_creative_id": ad_creative_id})
    
        if not payload:
            return _json({"error": "No update parameters provided (status, bid_amount, tracking_specs, or ad_creative_id)"})
    
        result = await make_api_request(ad_id, 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