Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_people_profile_phone

Updates the phone number for a specific CRM contact by people ID or email, keeping profile contact data current.

Instructions

Updates the phone number 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>",
      "phone": "<phone>"
    },
    "name": "update_people_profile_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesThe new phone number 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond "updates". It does not say whether the existing phone is overwritten, what happens if the profile has no phone, what permissions are required, or how invalid numbers are handled — significant gaps for a write operation on a named field.

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?

A single front-loaded sentence with the mutation and target stated up front and zero redundant wording. It is efficiently written, though the brevity reflects thin content rather than well-structured elaboration.

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 two-parameter mutation with no output schema, the schema fully covers the inputs, but the description omits behavioral context an agent would want before writing: overwrite semantics, error conditions, and permission requirements. Adequate to invoke correctly, incomplete for predicting consequences.

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%: both parameters are documented (people_id_or_email as the people_id or email, phone as the new number with an E.164 pattern). The description restates that a phone is being changed but adds no semantics beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ("Updates the phone number") scoped to "a specific CRM contact", which naturally distinguishes it from phone-adjacent siblings like set_conversation_phone and from the email/full_name/segments profile updaters. It stops short of naming any alternative explicitly, so it is clear but not fully differentiated.

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?

There is no when-to-use guidance, no exclusion of alternatives (e.g., when to use this versus update_people_profile_email or set_conversation_phone), and no note of prerequisites such as needing an existing people profile. The only implied context is that the target must be a CRM contact.

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