OneLence

Conversions

onelence_list_conversions

Read-onlyIdempotent

Lists individual conversions (purchases, sign-ups, leads and other conversion events OneLence tracked), newest first, each with its time, type, value and currency, attribution method, affiliate and coupon, plus how many conversions the window holds. Pass site for one site; without it, every site in the workspace. Visitor identities are never included.

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": "onelence_list_conversions"
  }
}

Input Schema

Name	Required	Description
`end`	No	Window end, inclusive for a date. Defaults to now.
`site`	No	Site domain (e.g. example.com) or site id. Defaults to the workspace's newest active site.
`limit`	No	Items to return (default 25).
`start`	No	Window start: a date (YYYY-MM-DD) or ISO 8601 date-time. Defaults to 30 days before end.
`cursor`	No	next_cursor from the previous call, for more.

Output Schema

Name	Required	Description
`data`	Yes
`more`	No	How to fetch the next page, when has_more.
`site`	Yes
`total`	Yes
`object`	Yes
`window`	Yes
`has_more`	Yes
`attribution`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "enum": [
+        "available",
+        "unavailable"
+      ],
+      "type": "string"
+    },
+    "data": {
+      "items": {
+        "properties": {
+          "affiliate": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "attribution": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "coupon": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "currency": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "object": {
+            "const": "conversion",
+            "type": "string"
+          },
+          "occurred_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "type": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "value": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "object",
+          "id",
+          "occurred_at",
+          "type",
+          "value",
+          "currency",
+          "attribution",
+          "affiliate",
+          "coupon"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "more": {
+      "description": "How to fetch the next page, when has_more.",
+      "type": "string"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "object": {
+      "const": "list",
+      "type": "string"
+    },
+    "site": {
+      "anyOf": [
+        {
+          "properties": {
+            "domain": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "domain"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total": {
+      "type": "number"
+    },
+    "window": {
+      "properties": {
+        "end": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "start": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "start",
+        "end"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "object",
+    "data",
+    "has_more",
+    "next_cursor",
+    "window",
+    "total",
+    "attribution",
+    "site"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish that this is a safe, idempotent, read-only read, so the bar is lower, and the description adds real value beyond them: result ordering (newest first), the fields per row, an accompanying window count, and the explicit privacy guarantee that visitor identities are never included. That last point is the kind of behavioral constraint an agent cannot learn from schema or annotations.

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?

Three sentences, front-loaded with the verb and payload, and every clause carries information (ordering, fields, count, privacy). The middle clause is dense and stacked with comma-separated fields, but nothing is filler.

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?

With a full input schema, an output schema, and rich annotations, the description only needs to cover scope, ordering, and exclusions — and it does. The one material hole is the incorrect description of the site default, which conflicts with what the schema declares.

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 coverage is 100%, so the baseline would be 3, but the description actively misstates the site parameter: it says "without it, every site in the workspace," while the schema says omitting site defaults to the workspace's newest active site. That is a direct conflict with the structured data on a parameter an agent will commonly omit, and it can produce a confidently wrong answer about data scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Lists individual conversions") and enumerates what counts as a conversion (purchases, sign-ups, leads) plus every field each row carries, so the agent knows exactly what it gets. It does not differentiate itself from near-neighbors like onelence_list_events or onelence_get_breakdown, leaving that inference to the agent.

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

Usage Guidelines3/5

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

The description explains the site-scoping behavior and the newest-first ordering, which hints at when to use it, but it never states when to prefer this over onelence_list_events, onelence_compare_sources, or onelence_get_breakdown. Usage is implied rather than directed.

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

All OneLence tools Inspect

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.