Skip to main content
Glama

ADS Beast

update_lead

Change fields on one existing lead: notes, assignee, contact details or pipeline stage. Only the keys supplied are written; the rest of the record is left as it is. A key that is not writable is refused with the list of fields that are, so a misspelled field cannot pass as a successful write.

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": {
      "lead_id": "<lead_id>",
      "fields": "<fields>"
    },
    "name": "update_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesObject of field name to new value, for example {"stage": "qualified", "notes": "Called back"}. Fields not listed keep their current value. Writable fields: assigned_to, company_name, contact_email, contact_name, contact_phone, estimated_monthly_budget, estimated_monthly_fee, expected_close_date, last_contact_at, lost_reason, notes, probability_pct, proposal_id, source, stage, tags, website.
lead_idYesADS Beast id of the lead to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare that this is a non-destructive, non-read-only, open-world mutation, so the description's job is narrow. It adds genuinely useful behavior beyond that: unwritten fields are preserved, and non-writable keys are rejected with the list of valid fields, which tells the agent that a misspelled field fails loudly rather than silently. It does not describe the success response, permissions, or rate limits.

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?

Three sentences, front-loaded with the action and scope, then partial-write semantics, then failure behavior. Every sentence contributes, though the final clause ('so a misspelled field cannot pass as a successful write') restates the preceding point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description would need to say what a successful call returns; it explains validation failure but not success shape. Combined with the omission of any guidance relative to move_lead_stage, it is adequate but leaves visible gaps for a mutation tool with a nested parameter.

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 100% and the nested 'fields' parameter already enumerates all writable fields with an example, so the schema carries the parameter burden. The description's mention of notes, assignee, contact details and pipeline stage only paraphrases a subset of that list without adding format or type detail.

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?

States a specific verb and resource ('Change fields on one existing lead') and enumerates the kinds of fields touched (notes, assignee, contact details, pipeline stage), which lets an agent distinguish it from read tools like get_lead. It does not name or contrast with the overlapping sibling move_lead_stage, so it stops short of full sibling differentiation.

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: 'one existing lead' and 'only the keys supplied are written' tell the agent this is an in-place partial update on an existing record, not a create. There is no explicit when-to-use/when-not guidance and no mention of when to prefer move_lead_stage for stage changes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.