Onsa

What to do next

list_next_steps

Read-onlyIdempotent

Returns read-only guidance for what to do next. Without campaignId, it returns the first-search question, active search progress, or campaign names and statuses to choose from. A single accessible campaign is resolved automatically. With campaignId, it returns a ranked to-do list: people who replied, people who accepted an invite but were never messaged, drafts and LinkedIn follow-ups waiting for approval, people with no reply for 7+ days while follow-ups are off, leads found but never contacted, and setup that is missing. It answers 'what should I do about this campaign today', where get_campaign_stats answers 'how is it doing'. For replies specifically, list_replies is the better source: its awaitingOurReply compares timestamps, while the replied bucket here covers only leads whose sentiment was scored and does not know whether we have since answered. leadIds passed to get_campaign_leads resolves the buckets into named people. Limits of the data: Onsa does not record whether we have already replied, or whether someone was contacted outside Onsa; 'replied' includes only replies whose sentiment was scored, so it is a floor; a withdrawn or unreachable invite leaves no trace, so some 'never contacted' leads may already have been tried. Sentiment is judged once per lead, not per message. Counts are complete; leadIds are capped at 200.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaignId`	No	Optional campaign to inspect; omitted for workspace guidance

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`items`	Yes
`scope`	No
`total`	No
`returned`	No
`campaigns`	No
`campaignId`	No
`leadsTotal`	No
`nextAction`	No
`campaignUrl`	No
`workspaceUrl`	No
`campaignTitle`	No
`workspaceState`	No
`searchAvailability`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 22, 2026

changedInput schema / properties / campaignId / description

Previous value: -"Campaign to inspect, from list_campaigns or fetch_leads"New value: +"Optional campaign to inspect; omitted for workspace guidance"

removedInput schema / required
```
Removed value: -[
-  "campaignId"
-]
```

addedOutput schema / properties / campaigns

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "campaignUrl": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "leadsTotal": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "status": {
+        "enum": [
+          "search_running",
+          "prospects_available",
+          "no_prospects"
+        ],
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "leadsTotal",
+      "status",
+      "campaignUrl"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / nextAction

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "arguments": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "question": {
+      "type": "string"
+    },
+    "reuseAuthorizedBrief": {
+      "type": "boolean"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / returned

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / scope

Added value: +{
+  "enum": [
+    "workspace",
+    "campaign"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / searchAvailability

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "allowance": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "limit": {
+              "type": "number"
+            },
+            "remaining": {
+              "type": "number"
+            },
+            "used": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "used",
+            "limit",
+            "remaining"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "reason": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "enum": [
+        "available",
+        "blocked",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "reason",
+    "allowance"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / total

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / workspaceState
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / workspaceUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "campaignId",
-  "campaignTitle",
-  "campaignUrl",
-  "leadsTotal",
-  "items"
-]New value: +[
+  "items"
+]

First observedSep 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower, yet the description adds substantial context: data limitations (Onsa doesn't record prior replies or off-platform contact), the 'replied' bucket as a floor, sentiment judged once per lead, no trace for withdrawn/unreachable invites, and leadIds capped at 200 while counts are complete.

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 core behavior, then alternatives, then limitations, with no filler sentences. It is dense and fairly long, but every clause carries actionable information; only minor tightening is possible.

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?

An output schema exists so return-value documentation is unnecessary, and the description instead covers the two invocation modes, bucket composition, sibling alternatives, and a thorough account of data limitations — complete for a read-only guidance tool of this complexity.

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 only one optional param exists, so the schema already documents campaignId. The description goes beyond it by explaining the omission path (workspace guidance, auto-resolution of a single accessible campaign) and the campaignId path (ranked to-do buckets), adding meaning the schema's one-line note doesn't.

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?

States a specific verb+resource (returns guidance for what to do next) and precisely delineates two modes: without campaignId it surfaces the first-search question, search progress, or campaign choices; with campaignId it returns a ranked to-do list. It names the buckets and explicitly distinguishes itself from get_campaign_stats ('how is it doing') and list_replies, so an agent can select it without opening the 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 routing: get_campaign_stats for campaign health, list_replies as the better source for replies (with the awaitingOurReply vs scored-sentiment rationale), and get_campaign_leads with leadIds to resolve buckets into people. When/when-not/alternative conditions are all present.

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

All Onsa 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.

Resources

Need Help?