Skip to main content
Glama

mureo_state_set_conversion_events

Define custom conversion events for a Meta ad account by specifying exact action_type strings, overriding the default conversion set to match the advertiser's real pixel events or component rows.

Instructions

Declare which Meta Insights action_type rows count as THIS account's conversions, overriding mureo's built-in deduped generic set (lead / purchase / complete_registration). Use this when an advertiser's real conversion is a CUSTOM pixel event (offsite_conversion.custom.<id>) — otherwise it reports 0 conversions — or when their account only emits a component row (e.g. offsite_conversion.fb_pixel_lead) with no generic aggregate. Replacement semantics: the listed action_types are the COMPLETE conversion set (never summed on top of the defaults), so overlapping alias rows can't double-count. Tip: to avoid typos, first call meta_ads_insights_report / _breakdown to see the account's real action_type labels, confirm with the operator, then set the exact string(s) here. Pass an empty list (or omit conversion_action_types) to CLEAR the override and restore the default. Stored on platforms[platform] and preserved across syncs. Returns the updated state document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional path to the file. Defaults to STRATEGY.md / STATE.json in the MCP server's current working directory. Paths outside cwd are refused.
platformYesPlatform key — normally ``meta_ads`` (the override only affects the Meta conversion counters).
account_idYesThe Meta ad account id (``act_*``). Always written onto the platform entry.
conversion_action_typesNoExact Meta ``action_type`` strings to count as conversions (e.g. ["offsite_conversion.custom.123"]). Empty / omitted clears the override.
Behavior4/5

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

With no annotations, the description carries full disclosure burden. It explains replacement semantics (complete set, no double-counting), clearing behavior (empty list restores defaults), and persistence (stored on platforms[platform] across syncs). It could mention permissions or risks, but overall transparent.

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?

The description is one paragraph but well-structured: starts with purpose, then usage, then semantics, then tips. It is concise with no fluff. Could benefit from brief sectioning, but it's efficient and front-loaded.

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

Completeness4/5

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

Given no output schema, the description mentions return value (updated state document). It covers purpose, usage, replacement semantics, clearing, and storage. For a moderately complex tool with 4 params, it is complete. Minor: could note that only affects Meta.

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%, so baseline is 3. Description adds significant value by detailing conversion_action_types format, the effect of empty/omitted values, and explaining the other parameters beyond their schema definitions. This warrants a 4.

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 clearly states the tool's purpose: declaring which Meta Insights action_type rows count as conversions, overriding defaults. It specifies the verb (set/override) and resource (conversion events for a Meta account), distinguishing it from siblings like mureo_state_upsert_campaign.

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

Usage Guidelines5/5

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

Provides explicit when-to-use scenarios (custom pixel events, component rows with no generic aggregate) and gives a practical tip to first call meta_ads_insights_report to verify action types. It also explains when to clear the override, offering comprehensive guidance.

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/logly/mureo'

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