Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppCreateParticipant

Add a participant to an inbox app conversation by person, user, or relationship ID, or by name, email, or phone when no ID is known.

Instructions

Add a participant to an inbox app conversation. Give exactly one of personId, userId, relationshipId, or name/email/phone.

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": {
      "inboxAppId": "<inboxAppId>",
      "extConversationId": "<extConversationId>"
    },
    "name": "inboxAppCreateParticipant"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName, if no ID is known.
emailNoEmail, if no ID is known.
phoneNoPhone, if no ID is known.
userIdNoFUB User ID. Mutually exclusive with the other ID fields.
personIdNoFUB Person ID. Mutually exclusive with the other ID fields.
inboxAppIdYesID of the inbox app making the call.
isAutomationNoTrue if the participant is an automated system. Default false.
relationshipIdNoFUB Relationship ID. Mutually exclusive with the other ID fields.
extConversationIdYesYour external ID of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.0.0
    • removedInput schema / properties / conversationId
      Removed value: -{
      -  "description": "Conversation ID",
      -  "type": "string"
      -}
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "Email, if no ID is known.",
      +  "type": "string"
      +}
    • addedInput schema / properties / extConversationId
      Added value: +{
      +  "description": "Your external ID of the conversation.",
      +  "type": "string"
      +}
    • addedInput schema / properties / inboxAppId
      Added value: +{
      +  "description": "ID of the inbox app making the call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / isAutomation
      Added value: +{
      +  "description": "True if the participant is an automated system. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Name, if no ID is known.",
      +  "type": "string"
      +}
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID to add"New value: +"FUB Person ID. Mutually exclusive with the other ID fields."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / phone
      Added value: +{
      +  "description": "Phone, if no ID is known.",
      +  "type": "string"
      +}
    • addedInput schema / properties / relationshipId
      Added value: +{
      +  "description": "FUB Relationship ID. Mutually exclusive with the other ID fields.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / userId
      Added value: +{
      +  "description": "FUB User ID. Mutually exclusive with the other ID fields.",
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "conversationId",
      -  "personId"
      -]New value: +[
      +  "inboxAppId",
      +  "extConversationId"
      +]
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds the field-exclusivity rule but does not disclose what happens if the participant already exists, whether retries create duplicates (relevant given idempotentHint=false), or what permissions the inbox app needs. Some added value beyond annotations, but the mutation-behavior story is incomplete.

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?

Two sentences, no filler, and the core action is front-loaded before the parameter rule. Every clause carries actionable information.

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 9-parameter mutation with no output schema, the definition covers purpose and the key exclusivity rule but leaves the conversation context (inboxAppId, extConversationId) and the response shape unaddressed. Adequate to invoke, thin on what to expect after the call.

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 per-field meanings are already covered, and the baseline would be 3. The description earns an extra point by stating the cross-field rule as a single 'exactly one of' constraint spanning personId, userId, relationshipId, and the name/email/phone fallback, which the schema only partially conveys through per-property 'mutually exclusive' notes.

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: 'Add a participant to an inbox app conversation.' That clearly separates it from the read-side sibling inboxAppGetParticipants and from the message/note siblings. It stops short of naming the sibling it replaces, 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 or when-not-to-use guidance. The description never says how this differs from inboxAppGetParticipants, or whether the conversation must already exist or be updated first. The 'exactly one of' sentence is a parameter constraint, not usage selection guidance.

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

Deploy Server

Other Tools