Skip to main content
Glama

Edit a company contact

editCompanyContact
Destructive

Create, change or deactivate a company contact. create: needs firstName + email; email is unique per company. Optional lastName, phone, linkedinUrl, title, calendarLink, isPrimary, shouldCc, slackTagging. Re-adding a removed email reactivates it. update: contactId + any fields to change. timezone takes an IANA zone like Europe/Berlin, null to clear. delete: contactId. Deactivates the contact (soft delete). set_primary: contactId. Makes it the company's primary contact. set_active: contactId + active. Reactivate (true) or deactivate (false). Ids come from readCompanyContacts list. calendarLink decides whose calendar the hiring manager's interview books on, so keep it correct. A role that needs its own link (a different link per role) takes it on the job tool's update calendarLink, not on a second contact.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "command": "<command>"
    },
    "name": "editCompanyContact"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNocreate (required) / update: contact's email (unique per company)
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
phoneNocreate/update: phone number
titleNocreate/update: job title at the company
activeNoset_active (required): true reactivates, false deactivates
commandYesWhich operation to run: create | update | delete | set_primary | set_active. The tool description explains each.
lastNameNocreate/update: contact's last name
shouldCcNocreate/update: whether to CC this contact on emails
timezoneNoupdate: the contact's IANA timezone like Europe/Berlin, null to clear; times in their emails use it
contactIdNoget/update/delete/set_primary/set_active (required): the contact's id from list
firstNameNocreate (required) / update: contact's first name
isPrimaryNocreate/update: mark as the primary company contact
linkedinUrlNocreate/update: LinkedIn profile URL
calendarLinkNocreate/update: calendar/scheduling link
slackTaggingNocreate/update: who Clera @-mentions on candidates and lists in the company's Slack channel. own_roles (default): tagged on roles they're hiring manager on; roles with no hiring manager go to the primary contact, or the earliest-added contact when none is primary. every_role: tagged on every candidate and list. never: never tagged, only named in plain text on their own roles. Set never when someone asks to stop being tagged.

Output Schema

NameRequiredDescriptionDefault
commandYes
contactNo
contactsNo
contactIdNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real substance on top: delete is a soft deactivate, re-adding a removed email reactivates it rather than creating a duplicate, email is unique per company, and calendarLink determines whose calendar the hiring manager's interviews book on. It also discloses that inputs and results are recorded for usage tracking and support, which an agent should know before sending contact data.

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?

The 'command:'-prefixed lines make it scannable despite covering five operations and the multi-command nature of the tool. Front-loading the purpose before the per-command detail is correct. A few clauses (the full re-statement of the slackTagging default) duplicate schema text and could be trimmed.

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?

For a 15-parameter, five-command mutation tool with an output schema, this is close to complete: it covers per-command inputs, the id source, soft-delete behavior, and the reactivation edge case. Missing are the outcome when create targets an already-active email (error vs. reuse) and any mention of orgId, but neither blocks correct invocation.

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 100%, so the baseline is 3; the description goes further by stating per-command requiredness (create needs firstName + email; update takes contactId plus any fields), which the schema cannot express since it only marks 'command' as required. It also specifies timezone is an IANA zone with null-to-clear semantics. The only notable omission is orgId, which the description never mentions.

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?

Opens with a concrete verb-and-resource statement ('Create, change or deactivate a company contact') and then enumerates the five distinct operations the single tool performs. It is clearly distinguished from readCompanyContacts (the source of ids) and from the job-level calendarLink update, so an agent can tell what this tool does and does not cover.

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?

Guidance is given per command ('create: needs firstName + email', 'delete: contactId', 'set_active: contactId + active'), plus explicit routing: ids come from readCompanyContacts, and a link that differs per role belongs on the job tool's update calendarLink rather than on a second contact. It also names the condition for slackTagging 'never' ('when someone asks to stop being tagged'), which is exactly the when-to-use signal an agent needs.

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.

Resources