Skip to main content
Glama
hermoso-ai

Hermoso

Official

Edit a Meta campaign / ad set / ad

update_meta_object
Idempotent

Update existing Meta ads: rename, adjust daily budget, change status (PAUSED/ACTIVE/ARCHIVED) or retarget ad sets. Activation requires confirmation to avoid accidental spend.

Instructions

Update an EXISTING campaign, ad set, or ad — rename, change its daily budget, retarget (ad sets), or change status (PAUSED / ACTIVE / ARCHIVED). Pass objectId (from list_meta_ads) + adAccountId. Setting something ACTIVE can start REAL AD SPEND — show the user what will run + its budget, get a yes, then pass confirm:true. Pausing / renaming / archiving is always safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNonew name
statusNoACTIVE starts spend (needs confirm:true); PAUSED / ARCHIVED are safe
confirmNoREQUIRED true ONLY to set status ACTIVE (real spend)
objectIdYesthe campaign / ad set / ad id (from list_meta_ads)
targetingNoreplacement targeting spec (ad sets) — a Meta targeting object
adAccountIdYesad account id (for auth + scope)
dailyBudgetUsdNonew daily budget in USD (1–10000; ad-set or campaign level)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
updatedNo
objectIdNo
Behavior5/5

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

Annotations indicate not read-only and not destructive. The description adds critical behavioral details: setting ACTIVE triggers real spend, pausing/renaming/archiving are safe, and confirm is mandatory for activation. No contradiction with annotations.

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 four sentences with clear front-loading of purpose, then key details, then critical warning. Every sentence adds value; no unnecessary words.

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

Completeness5/5

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

Given the high schema coverage, presence of output schema, and complexity of the tool (7 params, mutation with safety concerns), the description is complete. It covers all necessary usage context for safe invocation.

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?

Schema coverage is 100%, but the description adds value by mapping high-level operations to parameters (e.g., 'rename' → name, 'retarget' → targeting) and emphasizing the confirm requirement. It does not cover every param detail but enhances understanding.

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 action (update) and the resources (campaign, ad set, ad) and lists specific operations (rename, budget, retarget, status). It distinguishes from siblings like delete_meta_object and create_meta_campaign.

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

Usage Guidelines4/5

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

It provides clear prerequisites (objectId from list_meta_ads, adAccountId) and warns about real ad spend requiring user confirmation and confirm:true. It implies when not to use (creating instead of updating) but does not explicitly list all alternative tools.

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/hermoso-ai/hermoso'

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