Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

mureo_state_set_conversion_events

Override default conversion events for a Meta ad account by setting exact action_type strings, fixing zero conversions from custom pixel or component rows. Empty list restores defaults.

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). Use the SAME key the account is already stored under — one ad account has exactly one platform key, and a second key for an account another key already holds is REJECTED (the reporting view sums the entries, so it would double-count). A NEW key naming no platform mureo knows is REJECTED too.
account_idYesThe Meta ad account id (``act_*``). Always written onto the platform entry, and used to detect a second entry for the same account. The override applies ONLY to this account.
conversion_action_typesNoExact Meta ``action_type`` strings to count as conversions (e.g. ["offsite_conversion.custom.123"]). Empty / omitted clears the override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.1
    • changedInput schema / properties / platform / description
      Previous value: -"Platform key — normally ``meta_ads`` (the override only affects the Meta conversion counters). Use the SAME key the account is already stored under — one ad account has exactly one platform key, and a second key for an account another key already holds is REJECTED (the reporting view sums the entries, so it would double-count)."New value: +"Platform key — normally ``meta_ads`` (the override only affects the Meta conversion counters). Use the SAME key the account is already stored under — one ad account has exactly one platform key, and a second key for an account another key already holds is REJECTED (the reporting view sums the entries, so it would double-count). A NEW key naming no platform mureo knows is REJECTED too."
  2. Changed4 schema fields changedv0.10.43
    • changedInput schema / properties / account_id / description
      Previous value: -"The Meta ad account id (``act_*``). Always written onto the platform entry."New value: +"The Meta ad account id (``act_*``). Always written onto the platform entry, and used to detect a second entry for the same account. The override applies ONLY to this account."
    • addedInput schema / properties / account_id / minLength
      Added value: +1
    • changedInput schema / properties / platform / description
      Previous value: -"Platform key — normally ``meta_ads`` (the override only affects the Meta conversion counters)."New value: +"Platform key — normally ``meta_ads`` (the override only affects the Meta conversion counters). Use the SAME key the account is already stored under — one ad account has exactly one platform key, and a second key for an account another key already holds is REJECTED (the reporting view sums the entries, so it would double-count)."
    • addedInput schema / properties / platform / minLength
      Added value: +1
  3. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv1.0.7

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states replacement semantics (complete set, not additive), double-count prevention, storage location (platforms[platform]), persistence across syncs, return value (updated state document), and clearing behavior. This is thorough and leaves no ambiguity about side effects.

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 a single dense paragraph, but logically organized: purpose, use cases, replacement semantics, practical tip, clearing behavior, storage, and return value. Every sentence contributes value, though it could benefit from bullet points for readability. It is appropriately wordy for the complexity.

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

Completeness5/5

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

For a state-setting tool with no output schema, the description covers all necessary aspects: when to use, prerequisites (checking real action_type labels), exact semantics, clearing behavior, storage location, persistence, and return value. It is fully complete given the complexity and available structured metadata.

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 descriptions cover all 4 parameters (100% coverage), so the baseline is 3. The description adds practical context: exact string matching for conversion_action_types, the requirement that platform must be the same key used for the account (to avoid double-counting), and that account_id detects duplicate entries. This enhances schema information meaningfully.

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 for a specific account, overriding mureo's built-in generic set. It is distinct from sibling tools (like mureo_state_platform_metrics_set) by specifying the resource (conversion events) and the action (set/override). The phrase 'override the generic set' precisely identifies the operation.

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 guidance on when to use the tool: for custom pixel events (offsite_conversion.custom.<id>) or component rows without generic aggregate. It also advises calling meta_ads_insights_report / _breakdown first to verify exact action_type strings, and explains how to clear the override via an empty list or omission. This fully distinguishes it from alternatives.

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