Revnu

Get Lead

lead_get

Read-onlyIdempotent

One lead with its contacts (capped at 50; contactsTruncated says when). Read-only. In hosts that support MCP Apps, the user also sees this result in the Revnu app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Lead ID returned by leads_list or lead_get.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lead`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

changedOutput schema / properties / lead / properties / runPeople / description

Previous value: -"People the filtered workflow run added to this company's research list but not as contacts."New value: +"People the filtered workflow run returned on this company's research list but not as contacts."

addedOutput schema / properties / lead / properties / runPeople / items / properties / alreadyKnown

Added value: +{
+  "description": "True when the company already had this person before the run.",
+  "type": "boolean"
+}

addedOutput schema / properties / lead / properties / runPeople / items / properties / role

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "economic",
+        "champion",
+        "technical",
+        "user"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Part in the deal: economic is the buyer, champion the inside advocate."
+}

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / lead / properties / runPeople

Added value: +{
+  "description": "People the filtered workflow run added to this company's research list but not as contacts.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "email": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "linkedinUrl": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "photoUrl": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "profileUrl": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "title": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "name",
+      "title",
+      "email",
+      "linkedinUrl",
+      "profileUrl",
+      "photoUrl"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed12 schema fields changedOct 15, 2026

addedOutput schema / properties / lead / properties / archetype / description
```
Added value: +"Customer-defined buyer or company archetype."
```
addedOutput schema / properties / lead / properties / companyName / description
```
Added value: +"Company name, or null when not recorded."
```

changedOutput schema / properties / lead / properties / contact / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "email": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "linkedinUrl": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "name": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "photoUrl": {
-        "description": "Sourced profile photo; use it when displaying a person.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "title": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "email": {
+        "description": "Contact email address, or null when unknown.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "linkedinUrl": {
+        "description": "Contact's LinkedIn profile URL, when known.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "Contact's sourced full name, or null when unknown.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "photoUrl": {
+        "description": "Sourced profile photo; use it when displaying a person.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "title": {
+        "description": "Contact's job title, or null when unknown.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / lead / properties / contacts / items / properties / email / description
```
Added value: +"Contact email address, or null when unknown."
```
addedOutput schema / properties / lead / properties / contacts / items / properties / linkedinUrl / description
```
Added value: +"Contact's LinkedIn profile URL, when known."
```
addedOutput schema / properties / lead / properties / contacts / items / properties / name / description
```
Added value: +"Contact's sourced full name, or null when unknown."
```
addedOutput schema / properties / lead / properties / contacts / items / properties / title / description
```
Added value: +"Contact's job title, or null when unknown."
```

changedOutput schema / properties / lead / properties / createdAt / description

Previous value: -"Unix epoch milliseconds."New value: +"When this lead was saved, as Unix epoch milliseconds."

addedOutput schema / properties / lead / properties / fields / items / properties / key / description
```
Added value: +"Configured lead-column key."
```
addedOutput schema / properties / lead / properties / fields / items / properties / value / description
```
Added value: +"Stored column value, truncated to the API's display limit."
```
addedOutput schema / properties / lead / properties / tags / description
```
Added value: +"Labels assigned to this lead."
```
addedOutput schema / properties / lead / properties / vertical / description
```
Added value: +"Customer-defined industry category."
```

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / id / description

Added value: +"Lead ID returned by leads_list or lead_get."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "lead": {
+      "additionalProperties": true,
+      "properties": {
+        "archetype": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "companyName": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "contact": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "properties": {
+                "email": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "linkedinUrl": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "name": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "photoUrl": {
+                  "description": "Sourced profile photo; use it when displaying a person.",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "title": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Primary contact, when available."
+        },
+        "contacts": {
+          "description": "Up to 50 contacts on a detail read.",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "email": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "linkedinUrl": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "photoUrl": {
+                "description": "Sourced profile photo; use it when displaying a person.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "title": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "contactsTruncated": {
+          "description": "True when the contact cap was reached.",
+          "type": "boolean"
+        },
+        "createdAt": {
+          "description": "Unix epoch milliseconds.",
+          "type": "number"
+        },
+        "domain": {
+          "description": "Company website domain.",
+          "type": "string"
+        },
+        "fields": {
+          "description": "The customer's configured lead-column values.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "key": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "key",
+              "value"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "id": {
+          "description": "Lead ID for lead_get and lead_update.",
+          "type": "string"
+        },
+        "runContactIds": {
+          "description": "Contacts saved by the filtered workflow run.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "status": {
+          "description": "Qualification or outreach state.",
+          "type": "string"
+        },
+        "tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "vertical": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "domain"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "lead"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral detail beyond them: contacts are capped at 50 and `contactsTruncated` signals when that cap was hit, plus the MCP Apps rendering note. It stops short of describing not-found or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses, front-loaded with the payload shape, then the truncation caveat, then the read-only and UI notes. No filler or restatement of the title.

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?

For a one-parameter lookup with an output schema and full annotation coverage, the description supplies everything an agent needs: singular scope, the 50-contact cap and its truncation flag, and confirmation of read-only behavior. Return-value structure is correctly left to the output schema.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage, including its pattern and provenance, so the schema does the work. The description adds no additional meaning about the ID beyond what the schema already documents; baseline 3 applies.

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 and resource ('One lead with its contacts'), and the singular 'One lead' implicitly contrasts with the sibling leads_list, so an agent can route between them without opening a schema. Scope of the payload is also stated (contacts capped at 50).

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?

Usage is implied rather than stated: fetching a single lead by ID. The description never names leads_list as the alternative for enumerating leads, nor does it say what to do when the ID is unknown. The schema's note that the ID comes from leads_list or lead_get partially compensates, but the description itself gives no explicit when-to-use guidance.

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

All Revnu 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?