Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_people_profile_segments

Set or replace the segments assigned to a specific CRM contact by people ID or email, so you can organize and target contacts accurately.

Instructions

Updates the segments 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>",
      "segments": "<segments>"
    },
    "name": "update_people_profile_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
segmentsYesThe new list of segments 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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and says almost nothing: it does not state whether the supplied list replaces the entire segment set or is merged into it, whether the operation is idempotent, what permissions are required, or what happens on an unknown identifier. Only the bare fact of mutation is conveyed.

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?

It is a single front-loaded sentence with no filler, which is efficient. Brevity is close to under-specification, however, since nothing else is said about replace-vs-merge behavior.

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

Completeness2/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 annotations and no output schema, the definition should address the replace-vs-append semantics and error behavior. It leaves those out entirely, so an agent cannot predict the effect of the call from the description alone.

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%, so the schema already defines both parameters, including that segments is a minItems=1 array and that people_id_or_email accepts an id or email address. The description adds no format, validation, or edge-case detail beyond what the schema provides, 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 names a specific verb ('Updates') and resource ('segments of a specific CRM contact'), which clearly separates it from the sibling setters for email, full name, and phone. It does not explicitly name those siblings, but the resource is unambiguous.

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?

The target is implied by 'specific CRM contact', but there is no explicit when-to-use versus the other update_people_profile_* tools, no prerequisite statement, and no note on when a read (get_people_profile) should precede the write. Usage is inferred rather than stated.

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