freedom-mcp

Update lead

update_lead

Destructive

Edit an existing lead in the Leads CRM (crm_leads): name, email, phone, location, do-not-contact flag/reason, lifecycle state (new/active/flagged/archived), or the synopsis fields (title, company_name, tags, notes). Identify the lead with lead_id or email_lookup. Moving state to 'flagged' or 'archived' REQUIRES state_reason. Archiving sets archived_at (safe-archive, reversible — move state off archived to restore it). If the lead's outreach is set to auto and you move it off 'active', outreach is demoted back to manual (auto-outreach is only valid while active). Use when the operator or an agent needs to fix or maintain lead data — wrong email, bad name, DNC request, or a lifecycle move — instead of telling the user to edit it in the UI.

Routing: CRM/sales → edit a lead's fields, status, or DNC flag → use this (NOT update_lead_status/log_activity — those are removed)

[write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time. Call it on the first clear ask; the card is the yes — do not re-ask in chat.]

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New full name.
`tags`	No	Replacement tag list — folded into synopsis_jsonb.manual_entry.
`email`	No	New email (normalized to lowercase/trim). Rejected if it already belongs to another lead in this company.
`notes`	No	Notes about the lead — folded into synopsis_jsonb.manual_entry.
`phone`	No	New phone number.
`state`	No	New lifecycle state. state_reason is REQUIRED when moving to 'flagged' or 'archived'.
`title`	No	Job title — folded into synopsis_jsonb.manual_entry (other manual_entry keys are preserved).
`lead_id`	No	UUID of the lead to update. Provide this OR email_lookup.
`location`	No	New location.
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`company_name`	No	Company they work for — folded into synopsis_jsonb.manual_entry.
`email_lookup`	No	The lead's CURRENT email, used to find it. Provide this OR lead_id.
`state_reason`	No	Reason for the state change. Required when state is 'flagged' or 'archived'.
`do_not_contact`	No	Set true to flag the lead do-not-contact (excluded from outreach); false to clear it.
`do_not_contact_reason`	No	Reason for do_not_contact, e.g. 'customer', 'churned', 'opted_out'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only indicate write/destructive behavior, but the description adds substantial operational semantics: state_reason is required for flagged/archived, archiving is reversible and sets archived_at, auto-outreach is demoted to manual when leaving active, and DNC has an exclusion effect. This goes well beyond what the annotations provide.

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?

The description is long but well structured: core fields, identification, side effects, use case, routing, and approval flow each earn their place. It is denser than ideal for a quick scan, but the complexity of the tool justifies the length.

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 destructive 15-parameter update tool with no output schema, the description covers identification, required reasons for state changes, archival reversibility, outreach demotion behavior, DNC semantics, approval expectations, and routing. Nothing operationally critical is missing.

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%, so the baseline is 3, but the description adds meaning beyond the schema: it groups parameters conceptually, explains lead identification via lead_id or email_lookup, and reveals side effects like archived_at being set and auto-outreach being demoted. Some details remain schema-only, so not a 5.

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?

The description starts with a specific verb and resource: 'Edit an existing lead in the Leads CRM (crm_leads)' and enumerates the exact fields and lifecycle states involved. It also distinguishes itself from update_lead_status/log_activity, which removes ambiguity for an agent selecting among CRM-related tools.

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?

There is an explicit 'Use when...' statement covering the intended scenarios and a routing directive ('CRM/sales → edit a lead's fields, status, or DNC flag → use this'). It also names the sibling tools that should NOT be used, giving clear selection criteria.

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

All freedom-mcp 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?