Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_ad_account

Modify an ad account's name, spend cap, or timezone while leaving unspecified settings unchanged. Provide the account ID or use the configured default.

Instructions

Update the configured ad account settings. Only provided fields will be modified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew account name
spend_capNoAccount spend cap in currency cents (e.g. '100000' = $1000.00)
account_idNoAd account ID to update (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
timezone_nameNoNew timezone (e.g. 'America/New_York')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to update (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one genuinely important trait — that omitted fields are left untouched, i.e. non-destructive partial update — but says nothing about required permissions, whether the update is reversible, or what confirmation is returned. Adequate but incomplete for a mutation tool with zero annotation coverage.

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?

Two short sentences with no filler; the action is front-loaded and the partial-update caveat follows immediately. It is efficient, though slightly thin for the number of fields it governs.

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?

For a four-parameter mutation tool with no annotations and no output schema, the description covers the core semantics but leaves the agent without permission requirements, error behavior, or any indication of the response. The rich schema compensates for parameter documentation but not for the behavioral gaps.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents each of the four fields with types and examples (cents formatting, timezone string, account ID fallback). The description adds only the optionality rule, not format or constraint detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('Update the configured ad account settings'), clearly distinct from sibling mutations like update_campaign or update_adset. It stops short of naming which account is targeted (the schema's account_id / META_AD_ACCOUNT_ID fallback is the only place that appears), so it is clear but not fully self-contained.

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 sentence 'Only provided fields will be modified' implies a partial-update (PATCH-style) workflow, which is useful usage context. However, there is no explicit guidance on when to use this versus get_ad_account, list_ad_accounts, or other update_* tools, and no prerequisites or side-effect warnings are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools