Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_people_profile_email

Updates a CRM contact profile's email address using the person's ID or current email plus the new email, keeping contact records accurate.

Instructions

Updates the email address of a specific CRM contact.

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": {
      "people_id_or_email": "<people_id_or_email>",
      "new_email": "<new_email>"
    },
    "name": "update_people_profile_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_emailYesThe new email address for the CRM profile.
people_id_or_emailYesThe CRM profile people identifier or email address ('people_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It confirms this is an update operation but does not mention permissions, side effects, email uniqueness constraints, verification behavior, or what happens if the new email already exists.

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?

The description is a single concise sentence with the key action and target front-loaded. There is no unnecessary wording.

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?

For a simple two-parameter update tool with fully described schema fields and no output schema, the core operation is adequately described. However, because there are no annotations, additional behavioral detail about side effects and preconditions would improve completeness.

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 schema already explains both required parameters. The description adds no additional syntax, format, or lookup semantics beyond what the schema provides.

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: it updates the email address of a CRM contact. This clearly distinguishes the tool from siblings that update other profile fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description does not explain when to use this tool versus alternatives such as set_conversation_email or other profile update tools. It also gives no prerequisites or exclusions for changing a CRM contact email.

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