Skip to main content
Glama
Sign In

Nuira

by ai.nuira
OverviewDiscussionsAdmin

Channel performance

get_channels
Read-onlyIdempotent

Spend, revenue and ROAS per marketing channel (Meta, Google Ads, Klaviyo) over the whole period. QUOTE platform / platformRoas BY DEFAULT: each platform's own purchase claim, the figure Nuira's panels and recommendations use. Platform claims overlap (two platforms can claim one sale), so never add them up into store revenue. channels[].nuiraRevenue and nuiraRoas are Nuira's own attribution from Shopify touchpoints (measuredRevenue + modeledRevenue), a second opinion: quote them only when asked how Nuira attributes, and say so. previousPeriod.byChannel gives every one of these for the comparison period (previous by default, compare for last year). largestCampaign names a platform's campaign holding over half its claim, with roasWithout, the platform's ROAS without it. A channel with platform: null reported nothing — not zero. Optional from and to (inclusive YYYY-MM-DD, both or neither, never after today) read another span instead of the default period. A named month, a week or two dates the operator gave MUST be sent here: without them this reads the last 30 days, which is not that month.

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the span, inclusive, as YYYY-MM-DD; not after today. Send together with `from`, or omit both to read the default 30-day period.
fromNoFirst day of the span, inclusive, as YYYY-MM-DD. Send together with `to`, or omit both to read the default 30-day period.
compareNoWhat to compare the span with: previous (default, the same number of days just before), yoy (the same dates last year) or yoyWeekday (52 weeks back, the same weekdays — use it for natural Monday–Sunday weeks or whenever the operator says 'last year' over weeks).
compareToNoLast day of the named comparison period, YYYY-MM-DD.
compareFromNoFirst day of a NAMED comparison period, YYYY-MM-DD, with compareTo. For 'September with October': from/to October, compareFrom/compareTo the whole of September. Takes the place of compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / compareFrom
      Added value: +{
+  "description": "First day of a NAMED comparison period, YYYY-MM-DD, with compareTo. For 'September with October': from/to October, compareFrom/compareTo the whole of September. Takes the place of compare.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / compareTo
      Added value: +{
+  "description": "Last day of the named comparison period, YYYY-MM-DD.",
+  "format": "date",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / compare
      Added value: +{
+  "description": "What to compare the span with: previous (default, the same number of days just before), yoy (the same dates last year) or yoyWeekday (52 weeks back, the same weekdays — use it for natural Monday–Sunday weeks or whenever the operator says 'last year' over weeks).",
+  "enum": [
+    "previous",
+    "yoy",
+    "yoyWeekday"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"First day of the span, inclusive, as YYYY-MM-DD. Send together with `to`, or omit both to read the default 30-day period."
    • addedInput schema / properties / to / description
      Added value: +"Last day of the span, inclusive, as YYYY-MM-DD; not after today. Send together with `from`, or omit both to read the default 30-day period."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior the annotations cannot convey: platform claims overlap so they must never be summed into store revenue, a channel with `platform: null` reported nothing rather than zero, and the default window is the last 30 days. These are exactly the interpretation traps an agent would otherwise fall into.

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?

Front-loaded with the purpose and the default-quoting rule before the caveats, and nearly every sentence carries a decision-relevant fact. It is dense with parentheticals and repeats some of the from/to constraints already in the schema, which costs a little tightness but not comprehension.

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?

There is no output schema, so the description carries the full burden of return-shape disclosure and does it: it defines platform vs Nuira attribution, how measuredRevenue and modeledRevenue compose nuiraRevenue, the previousPeriod.byChannel structure, and largestCampaign with roasWithout. For a 5-parameter read tool with zero required params, nothing an agent needs to interpret results 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%, and the description still adds meaning beyond it: from/to are inclusive, must be sent together or not at all, and never after today; compare drives previousPeriod.byChannel with `previous` as default and last-year options; compareFrom/compareTo override compare for a named comparison period. The only soft spot is the phrasing '`compare` for last year', which is looser than the enum's yoy/yoyWeekday values, but the schema resolves it.

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?

Opens with a specific verb-and-resource statement: spend, revenue and ROAS per marketing channel, naming the actual platforms (Meta, Google Ads, Klaviyo) and the time scope. It then enumerates the returned fields (platform, platformRoas, nuiraRevenue, previousPeriod.byChannel, largestCampaign), which lets an agent separate this channel-level tool from siblings like get_campaigns or get_email_performance without opening a schema.

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?

Gives explicit defaults and exclusions: quote `platform`/`platformRoas` by default, quote `nuiraRevenue`/`nuiraRoas` only when the operator asks how Nuira attributes and label it as such. It also mandates a routing rule — a named month, week or explicit date pair MUST be sent as from/to because otherwise the tool silently reads the last 30 days. That is a when-to-use and when-not-to-use statement with an alternative behavior spelled out.

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

All Nuira toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources