Vendo AI

Create a lead manually

crm_create_lead

Add a lead card to the entry stage of the chosen pipeline(s). ALL fields optional — provide whatever is known (at least one of name/company/title/email/linkedin/phone). Not deduplicated (use crm_import_leads or crm_promote_contact_to_lead for dedup). Side-effect: a card appears on the customer board.

Input Schema

Name	Required	Description
`email`	No
`notes`	No
`phone`	No
`title`	No
`last_name`	No
`avatar_url`	No	Full http(s) URL
`branch_ids`	No	Pipelines to place the lead in: "general" and/or branch ids (default General)
`first_name`	No
`company_name`	No
`facebook_url`	No	Full http(s) URL
`linkedin_url`	No	Full http(s) URL
`instagram_url`	No	Full http(s) URL
`assigned_user_id`	No	Owner — user id from crm_list_workspace_members (default: you)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 26, 2026

addedInput schema / properties / assigned_user_id

Added value: +{
+  "description": "Owner — user id from crm_list_workspace_members (default: you)",
+  "type": "string"
+}

addedInput schema / properties / avatar_url

Added value: +{
+  "description": "Full http(s) URL",
+  "type": "string"
+}

addedInput schema / properties / branch_ids

Added value: +{
+  "description": "Pipelines to place the lead in: \"general\" and/or branch ids (default General)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / facebook_url

Added value: +{
+  "description": "Full http(s) URL",
+  "type": "string"
+}

addedInput schema / properties / instagram_url

Added value: +{
+  "description": "Full http(s) URL",
+  "type": "string"
+}

addedInput schema / properties / linkedin_url / description
```
Added value: +"Full http(s) URL"
```

addedInput schema / properties / notes

Added value: +{
+  "maxLength": 8000,
+  "type": "string"
+}

First observedJul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key traits: no deduplication, and the visible side effect that a card appears on the customer board. It does not cover failure modes (validation of email/phone, permission errors) or whether creation triggers integrations, which keeps it off 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the field rule, then the dedup routing, then the side effect. No filler and nothing buried.

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?

For a 13-parameter, zero-annotation, no-output-schema create tool, it covers purpose, intake minimum, dedup alternatives, and visible effect. Remaining gaps are modest (whether a lead id is returned, validation behavior) but real for a mutation tool.

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 only 46%, so the description must compensate, and it does the most valuable part: a cross-field constraint ('ALL fields optional … at least one of name/company/title/email/linkedin/phone') that no single schema property expresses. It still leaves notes, avatar_url, and branch_ids semantics to the schema, so it does not fully close the gap.

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?

A specific verb-plus-resource ('Add a lead card to the entry stage of the chosen pipeline(s)') that names the exact object and where it lands. It is immediately distinguishable from crm_import_leads and crm_promote_contact_to_lead, which it explicitly points to.

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?

States the alternative paths and the condition that selects them: bulk or deduplicated intake goes to crm_import_leads, converting an existing contact goes to crm_promote_contact_to_lead. It also spells out the create-time minimum (at least one of name/company/title/email/linkedin/phone), which is the practical gate on calling it.

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

All Vendo AI 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?