Automation and approvals: MCP tool reference
The Valkiria MCP server at https://valkiria.pro/mcp gives a connected assistant 24 tools for monitors, scheduled reports, the approval queue and the history of applied changes. 12 of them only read. The assistant picks the tool itself; this page lists what exists, under the names it reports in its tool calls.
01
Tools that read (12)
These only return data. They are not counted against the monthly allowance.
- workflows_list: Automation workflows of this account with status, run counts and the last run id. Read-only.
- workflow_run_status: Status, error and up to 50 steps of one workflow run owned by this account. Read-only.
- monitors_list: Monitors (agents) of this account: goal, watched metric and conditions, cadence, guardrails, last and next run, plus the metrics a monitor can watch. Read-only.
- monitor_runs: Past runs of one monitor, newest first: status, proposals and notifications created, what was skipped and why, errors. Read-only.
- monitor_test_run: Evaluate a monitor now against current metrics and show what it would notify about or propose, after guardrails. Dry run: no run is recorded, no notification is sent, no proposal is saved. Read-only.
- scheduled_tasks_list: What is delivered on a schedule for this account: the daily brief (on/off, cadence, channels) and every scheduled report with cadence, platforms, recipients and next run. Read-only.
- daily_brief_now: Build the account brief right now and return it: what changed, where the risk is, suggested actions and budget pace. Nothing is sent or saved. Read-only.
- approvals_list: Everything waiting for the owner's decision: care recommendations and queued operations (undos, restores, monitor proposals) with the reason, before/after, guard, how to undo and the expected spend direction. Read-only. Approval itself happens in the app or Telegram; use approval_link.
- approval_get: One proposal or queued operation by id, with its before/after snapshot, reason, status and the page where the owner decides. Read-only.
- approval_link: The page where the account owner approves or rejects pending changes, and how many are waiting. Assistants cannot approve or apply changes; give this link to the owner. Read-only.
- applied_changes_list: Changes Valkiria applied in the ad accounts, newest first, each with before/after, who initiated it, when, and whether it can be undone. Read-only.
- applied_change_impact: Compare the campaign's real platform metrics for equal windows before and after one applied change (the day of the change excluded). Answers not_enough_data when the after-window has not finished or days are missing; never extrapolates. Revenue and ROAS are null when the platform facts carry no revenue. Read-only.
02
Tools that change or generate (12)
A change requested through these tools follows the safety rules below: it is a proposal unless the write policy you set for the account allows it.
- decide_campaign_recommendation: Approve or reject a recommendation. Approving applies the change in the ad account at once and can change what is spent; preview it first. Assistants connected through sign-in (OAuth) can only reject: approving is done by the owner on the Campaign care page in Valkiria
- confirm_business_location: Confirm the business address of a cabinet (a found candidate by index, or a corrected address), reject a candidate, mark the client as not a physical business, or set the geo scope by option id. A confirmed address is what the audit and campaign building keep the ads around
- monitor_create: Create a monitor from a plain goal. It checks the account on a cadence and only notifies or queues proposals for the owner's approval; it never changes an ad account itself. Metrics: waste_watch = spend without conversions (threshold: minimum spend); cpa_guard = CPA rising (threshold: ratio to the reference CPA, e.g. 1.3); winner_boost = strong campaign (threshold: max CPA ratio to the account median, e.g. 0.8); no_impressions = enabled but not serving (threshold: days); ad_rejected = rejected ad (no threshold); spend_pace = spending ahead of the daily budget (threshold: ratio, e.g. 1.2). cadence manual = no schedule.
- monitor_update: Change a monitor: name, goal, metric / threshold, cadence, guardrails, or status (paused stops scheduled runs, active resumes them). Only the fields passed change. Nothing changes in an ad account.
- monitor_delete: Delete a monitor and its run history for good. Proposals it already queued stay in the approvals queue. To stop it temporarily use monitor_update with status paused.
- brief_schedule_set: Turn the account brief on or off and choose its cadence (daily, or weekly on Monday) and delivery channels: in_app, email, telegram. enabled=false pauses it and keeps the settings. The brief covers all connected platforms; it has no per-platform filter (use scheduled_report_create for that).
- scheduled_report_create: Create a report delivered by email on a cadence, for chosen platforms. Recipients default to the account email. Reports are built from stored platform facts; nothing changes in an ad account.
- scheduled_report_set_active: Pause (active=false) or resume (active=true) one scheduled report. Resuming skips missed runs and schedules the next one.
- scheduled_report_delete: Delete one scheduled report for good. To stop it temporarily use scheduled_report_set_active.
- report_generate_now: Run one scheduled report immediately, outside its schedule, and deliver it through its configured channel. For an ad-hoc analytics table use generate_report instead.
- approval_reject: Reject one pending proposal or queued operation and record why. Nothing changes in the ad account. There is no approve counterpart: approval stays with the owner in the app or Telegram.
- applied_change_request_undo: Ask to revert one applied change. This only queues the inverse change in the approvals queue under the write policy; the owner approves it in the app or Telegram. Nothing is written to the ad account by this tool.
03
How changes stay safe
- Two scopes, chosen by you at sign-in: read, and propose. With read alone the assistant cannot request any change.
- A change requested from an assistant is a proposal. It waits in Approvals in Valkiria until the account owner approves it, unless the write policy you set for that account allows that kind of change by itself.
- New campaigns are created paused. Starting new spend and deleting always wait for a person.
- The assistant can list what is waiting for approval and reject a proposal. It cannot approve one: approval stays with the owner in Valkiria.
- The change history shows who or what made each change and the value before and after, with Undo where the change can be reversed.
- You can disconnect an assistant at any time on the Connect AI page; a developer API key can be deleted the same way.
04
Limits
- The assistant sees only your own Valkiria workspace, and only the ad accounts connected there.
- Numbers are as fresh as the last sync or import; the assistant can tell you when that was.
- Money stays in each account's own currency. Different currencies are not converted or added up.
- Reading data is not counted against the monthly allowance; changes and AI generations are. Allowances per plan are on the pricing page.
05
FAQ
Connect an assistant and call the first tool
Create a free account, connect an ad account and add the connector. The first pass only reads.