Skip to main content
Glama

Customer LTV, cohorts and LTV:CAC

shopify_get_ltv
Read-only

Customer lifetime value from Shopify orders: average net sales per new customer within N days of their first order (LTV), contribution LTV after cost settings, repeat rate, new-customer CAC and LTV:CAC for Google, Meta, unattributed and all, plus monthly acquisition cohorts. Use for LTV, CAC payback, repeat purchase, retention or cohort questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shopify_get_ltv"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
limitNo
actionNo
statusNo
date_toNo
page_idNo
sort_byNo
user_idNo
site_urlNo
client_idNo
date_fromNo
ad_accountNo
ig_user_idNo
user_emailNo
range_presetNo
activity_onlyNo
campaign_nameNo
property_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is settled and the description is free to spend its words on computation semantics. It does so usefully: LTV is defined as net sales per new customer within N days of first order, contribution LTV depends on cost settings, and results are split by ad channel and monthly cohort. It does not mention default lookback windows, whether cost settings must be configured first, or result volume, which keeps it from a 5.

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?

Two sentences, both load-bearing: the first front-loads the core definition (LTV from orders) before piling on the metric list, and the second is a compact usage trigger. The metric enumeration is dense but each clause adds a distinct capability, so there is little waste; the long run-on first sentence is the only structural weakness.

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

Completeness3/5

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

An output schema exists, so return values need no prose, and the description adequately covers what the report contains and why an agent would call it. The remaining hole is input-side: with 19 optional parameters and no explanation of which ones actually shape the LTV calculation (days vs date_from/date_to vs range_preset), an agent has to guess at invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 19 parameters, so the description carries the full burden and largely does not meet it. Only 'days' is indirectly explained ('within N days of their first order'), and the channel split hints at an ad-account selector, but url, limit, action, status, date_from, date_to, range_preset, sort_by, page_id, user_id, client_id, site_url, user_email, ig_user_id, campaign_name, property_name and activity_only are all unexplained in both schema and description.

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 names a specific verb and resource ('Customer lifetime value from Shopify orders') and then enumerates the exact metrics computed: average net sales per new customer within N days of first order, contribution LTV after cost settings, repeat rate, new-customer CAC and LTV:CAC. It even breaks out the channel scopes (Google, Meta, unattributed, all) plus monthly acquisition cohorts, which clearly separates it from siblings like shopify_get_overview or the ad-platform summary tools.

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

Usage Guidelines4/5

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

The final sentence gives an explicit when-to-use list: 'LTV, CAC payback, repeat purchase, retention or cohort questions.' That is a clear routing signal for an agent choosing among analytics tools. It lacks any when-not guidance or named alternative (e.g. which tool to use for plain revenue or order counts instead), so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.