get_write_operations
The write operations an ad platform supports, and exactly what each takes.
For proposing a change you will not make yourself: an executable plan
(proposed_operations steps of {operation, operation_params, label})
the user reviews and applies. Without operations: every write
operation with its required parameters. With operations: each one’s
full parameter schema (types, descriptions, required). The account
identity is filled in when the plan runs, so it is never listed. The
same contract a plan is checked against before it is offered.
Derived from the platform’s write methods; no platform API call.
Returns: {“platform”, “operations”: [{operation, required} | {operation, parameters, required}], “note”, and “unknown”/“available” for names the platform cannot write}
Parameters#
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
platform | string | yes | The ad platform. Values: ‘google_ads’, ‘meta_ads’, ‘microsoft_ads’, ‘chatgpt_ads’, ‘applovin_ads’, ‘universal_ads’, ‘tiktok_ads’, ‘dv360_ads’, ‘sklik_ads’. | |
operations | array | no | Operations to describe in full, e.g. [“update_location_targeting”]. Omit for the index of every write operation. |
Generated by generate_mcp_docs from the server tool. Add to this page below this block; the block is rewritten on every run.