Skip to main content
Glama

Add to CRM

Add a person to the CRM

add_person_to_crm

Add a person to the customer's connected CRM. It looks the person up from the profile link, e-mail or name given, checks the CRM first so nobody is added twice, and saves what it found with the customer's usual field settings and default tags. A record with the same name is reported as a possible match and nothing is added until add_anyway is set. Uses one lookup credit when an e-mail address is found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_person_to_crm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNothe person's full name; give it with a company when there is no profile link or e-mail
tagsNotags to put on the record, in addition to the customer's default tags
emailNoan e-mail address the person is known by
companyNothe company the person works for
use_emailNoone of the addresses found, to save as the person's main e-mail instead of the best one
add_anywayNotrue to add the person although a possible match exists, once that match is known to be a different person
profile_urlNolink to the person's public profile page
include_phoneNoalso look for a mobile number; this uses extra credits, so set it only when the customer wants a phone number saved

Output Schema

NameRequiredDescriptionDefault
crmNothe CRM the person was added to, or checked
recordNothe new record, or the one already there
statusNoadded, already_in_crm, possible_matches, not_found or pending
contactNowhat was found for the person and saved
not_savedNofields the CRM did not take, when any
credits_leftNo
credits_usedNo
possible_matchesNorecords that share the person's name and may or may not be the same person

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / contact / properties / emails / items / properties / status / description
      Previous value: -"how sure we are the address is deliverable (verified, likely, unverified, risky)"New value: +"how sure we are the address is deliverable (verified, accept_all, unverified, guessed)"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only declare readOnly=false, openWorld=true, idempotent=false and destructive=false; the description adds genuinely new behavior — pre-write deduplication, the blocked-write safety gate on possible matches, the fact that the customer's usual field settings and default tags are applied, and that a lookup credit is consumed when an e-mail is found. Credit consumption and the partially-committed match state are exactly the kind of non-obvious traits annotations cannot express.

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 then the workflow, with no filler or marketing language. The middle sentence is long and chains lookup, dedupe, save-settings and tagging together, which makes it slightly harder to scan than it needs to be.

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 8 all-optional parameters, an output schema and full annotations, the description covers what an agent needs: lookup sources, duplicate handling, the add_anyway gate and credit cost. The one residual gap is that it does not say what the tool does when no usable identifier is supplied, which matters given that zero parameters are required.

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 already 100%, so the baseline is 3; the description earns an extra point by explaining how parameters interact rather than restating them — that profile_url, email and name are alternative lookup keys, and that add_anyway is the override that only makes sense once a possible match has been reported. It does not add much on tags, use_email or include_phone beyond what the schema already documents.

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 states a specific verb and resource ('Add a person to the customer's connected CRM') and, through the singular 'person', implicitly separates itself from the batch sibling add_people_to_crm and from add_company_to_crm. It also characterizes the operation as a lookup-then-save workflow rather than a blind insert, which further distinguishes it from update_crm_record.

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?

It gives clear operating context: the person is resolved from profile link, e-mail or name, an existing-record check runs first, and a same-name hit blocks the add until add_anyway is set. What it lacks is explicit routing — it never names add_people_to_crm for bulk work or confirm_possible_match as the step that resolves a match, so the agent must infer those handoffs.

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.