Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Update lead

update_lead

Modify fields on one lead by sending only changed values; include expectedUpdatedAt to reject stale writes and use null to clear phone, email, city, or notes.

Instructions

Change fields on one lead. Send only the fields that change. Pass expectedUpdatedAt from the last read to reject a stale write. Null clears phone, email, city, or notes. Money stays in integer cents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "leadId": "<leadId>"
    },
    "name": "update_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
emailNoNull clears the email address.
notesNo
phoneNoNull clears the phone number.
stageNo
leadIdYes
sourceNo
serviceNo
urgencyNo
contactNameNo
expectedUpdatedAtNoOptimistic concurrency token. Pass the updatedAt you last read. The update is rejected if the lead changed.
estimatedValueCentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, closed-world); the description adds real behavioral context beyond that: partial-update semantics, stale-write rejection via expectedUpdatedAt, and which fields are cleared by null. It still omits whether unspecified fields are preserved verbatim and what a successful response contains.

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?

Five short sentences, each carrying a distinct rule: patch semantics, concurrency token, null-clearing set, and money units. The highest-risk ambiguity (stale writes) is stated up front with zero 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?

For a 12-parameter mutation tool with no output schema and thin schema descriptions, the description covers the highest-risk ambiguities: partial updates, optimistic concurrency, null clearing, and unit conventions. The remaining gaps are the return shape and any permission or validation failure behavior, which an agent would want but can often discover at call time.

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?

Schema description coverage is only 25% across 12 parameters, so the description must carry weight. It explains expectedUpdatedAt, null-clearing for phone/email/city/notes, and that money is integer cents, but stage, source, service, urgency, and contactName get no semantic treatment beyond their raw schema constraints.

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?

"Change fields on one lead" gives a specific verb (change/patch), a specific resource (a single lead), and scope (one record, partial field set). It is clearly distinguishable from create_lead or search_leads by the patch semantics, though it never names a sibling explicitly.

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?

"Send only the fields that change" tells the agent how to invoke it (partial update rather than full replace), which implies when it is appropriate. However, there is no explicit when-not guidance, no mention of create_lead for new records, and no stated preconditions such as reading the lead first to obtain expectedUpdatedAt.

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