mcp

tag_contact

DestructiveIdempotent

Add or remove tags on a contact. Tags are flat labels — vip, beta, churned — as opposed to custom properties, which are declared fields with a value. They are lower-cased and spaces become hyphens, so VIP and vip are the same tag. Tagging reaches the person across every audience they are on. list_tags returns the tags the workspace already uses, so an existing tag can be reused rather than a synonym created. Adding a tag an automation exits on (e.g. customer), or removing one it requires (e.g. trial), ends the person's enrolment in it at once. Adding a tag the contact did not already carry starts every active automation with a tag_added trigger on it, so a tag can put someone on a sequence; list_automations shows each automation's trigger. Returns the contact, as get_contact does, with its tags after the change. list_automation_enrollments with status 'canceled' shows which enrolments a tag change ended, with each row's cancel_reason (exit_tag or required_tag_missing).

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": {
      "contact_id": "<contact_id>"
    },
    "name": "tag_contact"
  }
}

Input Schema

Name	Required	Description
`add`	No
`remove`	No
`contact_id`	Yes	The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. find_contact returns the id for an address.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedInput schema / properties / contact_id / description

Previous value: -"The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. Call find_contact with the address first if that is all you have."New value: +"The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. find_contact returns the id for an address."

Changed4 schema fields changedSep 15, 2026
- addedInput schema / properties / add / items / minLength
```
Added value: +1
```
- addedInput schema / properties / add / maxItems
```
Added value: +50
```
- addedInput schema / properties / remove / items / minLength
```
Added value: +1
```
- addedInput schema / properties / remove / maxItems
```
Added value: +50
```

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / contact_id / description

Added value: +"The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. Call find_contact with the address first if that is all you have."

First observedSep 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare the safety profile (destructiveHint=true, idempotentHint=true, openWorldHint=true), and the description adds substantial context beyond them: normalization rules (lowercasing, spaces to hyphens), the fact that tagging crosses every audience the person is on, and the automation side effects (adding an exit tag or removing a required tag ends enrolment; adding a new tag fires tag_added automations). This is exactly the extra behavioral detail 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?

Front-loads the core action and distinction in the first two sentences, then layers side-effect and sibling information. It is fairly long at eight sentences, but nearly every sentence carries distinct, actionable content; a small amount of consolidation is possible.

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

Completeness5/5

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

There is no output schema, and the description compensates by stating the return value ('Returns the contact, as get_contact does, with its tags after the change'). Combined with normalization, cross-audience scope, and automation side effects, an agent has everything needed to call and interpret this tool correctly.

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 only 33% — only contact_id is documented in the schema — so the description must compensate, and it does: it explains that tags are lower-cased with spaces becoming hyphens (VIP == vip), which directly tells the agent how values passed in add/remove will be normalized. It stops short of describing the add/remove array semantics (e.g. max 50, empty-array behavior) explicitly.

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?

States a specific verb (add/remove) and resource (tags on a contact), and explicitly disambiguates from custom properties ('flat labels... as opposed to custom properties, which are declared fields with a value'). An agent can distinguish it from update_contact, list_tags, and other siblings without opening a schema.

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

Usage Guidelines5/5

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

Routes the agent explicitly: use list_tags to reuse an existing tag rather than create a synonym, use list_automations to see a tag_added trigger, and use list_automation_enrollments with status 'canceled' to see which enrolments a change ended. These are concrete when-to-use and where-to-look instructions, not implied context.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.