Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

mureo_state_set_conversion_events

Set exact Meta action_type strings that count as conversions for an ad account, overriding default lead/purchase to fix zero-conversion reports. Pass an empty list to clear the override.

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.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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. A placeholder (``unknown``, ``n/a``, …) is refused.
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.21.3
    • changedInput schema / properties / account_id / description
      Previous 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."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. A placeholder (``unknown``, ``n/a``, …) is refused."
  2. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  3. 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."
  4. 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
  5. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  6. Addedv1.0.7

TDQS

A4.9/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—and it delivers. It discloses replacement semantics (the listed action_types are the COMPLETE set, never summed), the clearing behavior, persistence across syncs, storage location, and the return value. It also explains the failure mode it prevents (reporting 0 conversions). This is exemplary transparency for a state-mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: purpose, use cases, override semantics, verification tip, clearing behavior, persistence, and return value. It is front-loaded with the core purpose and usage conditions, then moves to mechanics. No redundancy or filler.

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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is remarkably complete. It covers why (0-conversion problem), when (custom/component events), how (replacement semantics), how to verify (call insights report), how to undo (empty list), where state lives (platforms[platform]), and what it returns (updated state document). Nothing an agent needs to call it correctly is missing.

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% with detailed parameter descriptions, so the baseline is 3. The main description adds meaning beyond the schema by explaining the built-in default set, the exact-string requirement for action_type labels, the double-count risk with overlapping aliases, and the empty-list clear semantics. This is valuable framing that helps an agent choose correct parameter values.

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 uses a specific verb ('Declare') and resource ('which Meta Insights action_type rows count as THIS account's conversions'), clearly distinguishing this from sibling state tools like mureo_state_platform_metrics_set and Google Ads conversion tools. It also explicitly references the built-in defaults being overridden, leaving no ambiguity about the tool's function.

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?

It states exact conditions for use: when the advertiser's conversion is a custom pixel event or when only a component row exists. It also gives a concrete workflow tip (call meta_ads_insights_report first to see real labels) and explains how to clear the override with an empty list. This leaves no doubt about when to invoke this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools