Skip to main content
Glama
Sign In

Vendo AI

by com.vendo-ai
OverviewDiscussionsAdmin

List CRM leads

crm_list_leads

List leads in the CRM pipeline. Filters: branch ("general" or a branch id from crm_list_branches; omitted = all branches visible to the user), stage (stage id), owner (user id from crm_list_workspace_members), source, q (name/company/email search), range or from/to, limit/offset. Read-only. Great first call for "who replied to me?".

Input Schema

NameRequiredDescriptionDefault
qNo
toNoISO date — created to
fromNoISO date — created from
limitNo
ownerNoAssigned user id
rangeNoOmit for all time
stageNo
branchNo
offsetNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "ISO date — created from",
+  "type": "string"
+}
    • addedInput schema / properties / owner
      Added value: +{
+  "description": "Assigned user id",
+  "type": "string"
+}
    • addedInput schema / properties / range / description
      Added value: +"Omit for all time"
    • addedInput schema / properties / range / enum
      Added value: +[
+  "24h",
+  "7d",
+  "30d",
+  "90d",
+  "180d",
+  "1y"
+]
    • addedInput schema / properties / source / enum
      Added value: +[
+  "linkedin_outreach_reply",
+  "linkedin_inbound",
+  "linkedin_manual",
+  "email_reply_real",
+  "widget_chat",
+  "widget_voice",
+  "widget_form",
+  "narrator_form",
+  "telegram_message",
+  "whatsapp_message",
+  "phone_call_interested",
+  "meeting_booked",
+  "crm_integration_inbound",
+  "manual"
+]
    • addedInput schema / properties / to
      Added value: +{
+  "description": "ISO date — created to",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / branch
      Added value: +{
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose two important traits: the operation is read-only, and omitting branch means 'all branches visible to the user' (permission scoping). However it says nothing about result ordering, pagination behavior, or default page size, which matter for a 10-param list tool with a 200 limit.

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?

Front-loaded with purpose, then a compact filter enumeration, then a behavioral note and usage hook. Dense with facts and free of filler; the parenthetical value sources earn their space.

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 10 params, no annotations and no output schema, the filter semantics are well covered. The remaining gap is the response shape — what a lead row contains and how pagination/order behaves — which the description leaves entirely implicit.

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 40%, but the description compensates well: it names the value source for branch and owner, explains the omission default for branch, and clarifies q searches name/company/email. Only limit/offset lack added meaning beyond their integer bounds, but that is a small residual 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?

States a specific verb and resource ('List leads in the CRM pipeline') and immediately scopes it with the filter set, which cleanly separates it from single-lead siblings like crm_get_lead and from crm_list_stages / list_narrator_leads. An agent can pick this tool 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 Guidelines4/5

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

Provides real usage context: 'Read-only' plus 'Great first call for "who replied to me?"' tells the agent this is a broad entry point. It also routes the agent to crm_list_branches and crm_list_workspace_members for valid filter values. It stops short of explicit exclusions (e.g. use crm_get_lead for a single lead), so not a 5.

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

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