Markifact - Ads & Analytics

Search for available Markifact operations that can be executed by the authenticated user. Workflow: find_operations → get_operation_inputs → run_operation (read-only) or run_write_operation (when requires_approval: true). After selecting an operation_id, always call get_operation_inputs next. Never call run_operation / run_write_operation without first inspecting the schema via get_operation_inputs. Input shapes, nested objects, and field names vary per operation and cannot be guessed. Returned operation IDs are registry-backed Markifact operation IDs, not arbitrary action names.

find_operations

Get a signed URL for a private file. Use this when an operation returns a `file_id` and you need a temporary, directly accessible URL. Operation `file_url` values are user-facing app URLs that require Markifact authentication; call this tool to generate a signed URL that the model or external tools can open directly. The signed URL expires after 1 hour.

get_file_url

Get the input schema, required fields, defaults and constraints for an operation. Required step between find_operations and run_operation/run_write_operation. Call this once per operation_id before executing it — schemas contain nested objects, account selectors, and field names that vary per operation and cannot be guessed. If you already retrieved the schema for this operation_id earlier in the conversation, reuse it instead of calling again. Only pass fields from this schema in run_operation/run_write_operation input_data for the same operation_id. Do not include unrelated context or data outside the selected operation schema.

get_operation_inputs

List saved Markifact connections for an app/platform. A connection is a saved authenticated integration in Markifact. The returned `id` is the `connection_id` used to choose which saved login/integration an operation should use. Important: - `connection_id` is not an external platform account ID. - External account IDs, customer IDs, property IDs, and similar values are separate operation inputs. - One connection may have access to multiple external accounts. - In most cases, you don not need to provide `connection_id`. If the user has only one connected login for a platform in their workspace, operations usually use that connection automatically. Use this tool only when the user wants a specific saved integration or has multiple connections for the same platform.

list_connections

Create a signed upload URL for a media file selected in the upload UI.

prepare_media_upload

Inspect a file returned by a previous operation as numbered lines of text. Use this when an operation returns a `file_id` and you want to inspect the file contents before deciding what to do next. This is mainly useful for exported JSON, CSV, logs, and similar files produced by Markifact operations. It returns the file as numbered text lines so you can quickly review the structure, schema, headers, sample rows, or specific sections in chunks.

read_file

Submit actionable product feedback to Markifact with the user's authorization. When you encounter a likely Markifact bug, missing capability, or product limitation while completing a task, proactively tell the user what you found and offer to report it to Markifact. You may draft a concise proposed report for the user to review. Call this tool only after either: 1. the user explicitly asks you to submit the feedback, or 2. you offered to report a discovered issue and the user explicitly agreed. If the user's request already clearly authorizes submission, do not ask for redundant confirmation. Do not call this tool merely to ask for permission, and do not submit feedback silently. This tool creates an irreversible feedback submission in Markifact's support workflow. The submission contains the supplied feedback, relevant operation IDs, and account-associated contact and reference identifiers. After a successful call, briefly tell the user that the feedback was submitted. Before proposing a report, distinguish a Markifact issue from an external API, platform, or user-configuration limitation. Do not propose reports for third-party policies, outages, rate limits, rejected content, campaign performance, or user configuration unless Markifact itself caused or mishandled the issue. For a potentially missing integration capability, use the normal operation discovery flow to check whether Markifact already provides a dedicated or generic operation that supports the requested action. Do not execute a write operation merely to test whether a capability exists. Include only the minimum non-sensitive concrete evidence needed to understand the issue. Never include passwords, API keys, access tokens, authentication details, payment information, raw conversation history, complete request or response payloads, or unrelated personal or customer data. Summarize relevant errors and behavior instead of copying raw data. Avoid duplicate or repetitive reports. Use `other` only when the feedback does not fit another category. Write the title and description in English. Do not promise that Markifact will respond or implement a fix.

report_markifact_feedback

Execute a **read-only** Markifact operation, such as fetching reports, listing records, selecting accounts, or looking up account details. Use this in direct response to the user's current request. Do not use it for startup checks or background context gathering. For write/create/update/delete actions, use `run_write_operation` instead. Operations returned by `find_operations` with `requires_approval: true` MUST be executed via `run_write_operation`. operation_id must be an exact Markifact operation ID returned by find_operations for the authenticated user.

run_operation

Execute a **write** operation that creates, updates, or deletes external data. Use this tool ONLY for operations marked with `requires_approval: true` in `find_operations` results. These are destructive actions like creating campaigns, updating ad statuses, sending emails, etc. operation_id must be an exact Markifact operation ID returned by find_operations for the authenticated user. **APPROVAL REQUIRED**: Every call writes irreversibly to the user's live external accounts. Before each invocation, summarize the exact change in plain language (operation, target account/resource, key field values) and wait for explicit user confirmation. Never call without user's confirmation, approval is CRITICAL.

run_write_operation

Upload an image or video asset for later operations. Use this when the user needs to provide media that will be reused in later tool calls, for example creating Facebook ad image or video asset, or a Google Ads creative flow. The tool returns file URLs that can be passed into later operations that accept uploaded media. Only image and video uploads are supported.

upload_media