Skip to main content
Glama

mureo_state_platform_metrics_set

Set platform metric rollups in STATE.json to update the dashboard's per-platform KPIs and period toggle without re-querying. Writes totals for the most recent window or per-window rollups.

Instructions

Atomically set a platform's metric ROLLUP in STATE.json's v2 platforms section so the read-only reporting dashboard can render per-platform KPIs (and the YESTERDAY / LAST_30_DAYS period toggle) without re-querying. This writes the PLATFORM-LEVEL rollup — distinct from mureo_state_upsert_campaign, which writes per-campaign metrics. Pass totals + metrics_period for the single most-recent window, and/or periods ({"YESTERDAY": {…}, "LAST_30_DAYS": {…}}) for the per-window rollups the toggle reads. periods is merged per window key (a YESTERDAY write keeps a prior LAST_30_DAYS bucket); omitted fields preserve their existing value. Campaigns and every other platform are preserved. account_id is required and always written onto the entry. Returns the updated state document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesPlatform key: a built-in (``google_ads`` / ``meta_ads`` / ``search_console`` / ``ga4``) or a plugin bridge ``plugin:<dist>``.
account_idYesThe platform account id (Google customer_id / Meta act_*). Always written onto the platform entry.
totalsNoSingle-rollup totals for the most recent window (spend, impressions, clicks, conversions, cpa, ctr, result_indicator, period, fetched_at). Omit to preserve the existing value.
metrics_periodNoThe window ``totals`` covers (e.g. ``LAST_30_DAYS``). Omit to preserve the existing value.
periodsNoPer-window rollups keyed by period token (``YESTERDAY`` / ``LAST_30_DAYS`` / …); each value is a totals-shaped object. Merged per key into the existing map. Omit to preserve the existing map.
pathNoOptional path to the file. Defaults to STRATEGY.md / STATE.json in the MCP server's current working directory. Paths outside cwd are refused.
Behavior4/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 discloses atomic write, merge semantics for periods, and preservation of unrelated data. However, it does not mention potential error conditions or idempotency guarantees, which would further improve transparency.

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 well-structured with front-loaded purpose and key details. It is slightly verbose but every sentence adds value (differentiation, behavioral nuances). Could be slightly more concise by grouping related info, but overall effective.

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 6 parameters with nested objects and no output schema, the description adequately explains the input behavior, merge strategy, and preservation of other data. It mentions 'Returns the updated state document' which suffices for a write operation. Covers the essential context for correct usage.

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 good descriptions, but the description adds important behavioral context beyond schema: explains that periods are merged per window key, omitted fields preserve existing values, and account_id always written. This helps the agent understand the merge semantics and side effects.

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?

Description clearly states it atomically sets a platform metric rollup in STATE.json's platforms section for the reporting dashboard. It explicitly distinguishes from mureo_state_upsert_campaign which writes per-campaign metrics, so the agent knows exactly which tool to use for platform-level rollups.

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 this tool vs the sibling mureo_state_upsert_campaign. Also explains the behavior of periods merging, preservation of omitted fields and other entities, and the requirement to pass account_id, giving clear context for correct usage.

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