Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppUpdateConversation

Update inbox app conversation details—subject, archive state, person, or assignment—by sending only the fields that need to change.

Instructions

Update an inbox app conversation: subject, archive state, person, or assignment. Send only fields to change.

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": "inboxAppUpdateConversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
personNoUpdates the person; only allowed if no Person ID is set yet.
subjectNoSets or updates the conversation subject.
archivedNoArchive or unarchive the conversation.
inboxAppIdYesID of the inbox app making the call.
assignedUserIdNoUser to reassign to. 0 reverts to the conversation owner.
assignedInboxIdNoTeam Inbox to reassign to. 0 reverts to the conversation owner.
extConversationIdYesYour external ID of the conversation to update.
permanentlyArchivedNoDisables replies/notes; users cannot un-archive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "Archive or unarchive the conversation.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / assignedInboxId
      Added value: +{
      +  "description": "Team Inbox to reassign to. 0 reverts to the conversation owner.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / assignedUserId
      Added value: +{
      +  "description": "User to reassign to. 0 reverts to the conversation owner.",
      +  "type": "integer"
      +}
    • removedInput schema / properties / conversationId
      Removed value: -{
      -  "description": "Conversation ID",
      -  "type": "string"
      -}
    • addedInput schema / properties / extConversationId
      Added value: +{
      +  "description": "Your external ID of the conversation to update.",
      +  "type": "string"
      +}
    • addedInput schema / properties / inboxAppId
      Added value: +{
      +  "description": "ID of the inbox app making the call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / permanentlyArchived
      Added value: +{
      +  "description": "Disables replies/notes; users cannot un-archive.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / person
      Added value: +{
      +  "description": "Updates the person; only allowed if no Person ID is set yet.",
      +  "properties": {
      +    "email": {
      +      "description": "Email, for people not yet in FUB.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "FUB Person ID.",
      +      "type": "integer"
      +    },
      +    "name": {
      +      "description": "Name, for people not yet in FUB.",
      +      "type": "string"
      +    },
      +    "phone": {
      +      "description": "Phone, for people not yet in FUB.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • removedInput schema / properties / status
      Removed value: -{
      -  "description": "New status",
      -  "type": "string"
      -}
    • addedInput schema / properties / subject
      Added value: +{
      +  "description": "Sets or updates the conversation subject.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "conversationId"
      -]New value: +[
      +  "inboxAppId",
      +  "extConversationId"
      +]
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent write, and the description adds the meaningful partial-update semantics on top of that. It does not, however, disclose permissions, what happens to omitted fields beyond 'unchanged', or any error/response behavior.

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 short sentences, front-loaded with the action and the affected fields, with the operational rule second. Nothing is redundant or padded.

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 an 8-parameter mutation with a nested object and no output schema, the description is thin: it omits return behavior, whether repeated calls are safe, and the conditional constraint on person updates. The rich schema compensates substantially, but the definition still leaves gaps an agent would care about.

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 each parameter including the nested person object and the 0-reverts-to-owner semantics is already documented; the description only echoes the field list. Baseline 3 applies since the schema carries the semantic load.

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 ('Update') and resource ('inbox app conversation') and enumerates the mutable facets: subject, archive state, person, assignment. It is clearly distinct from neighbors like inboxAppUpdateMessage or updatePerson, though it never explicitly says how it differs from them.

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?

'Send only fields to change' gives a real partial-update convention, which is useful usage guidance, but there is no statement of when to prefer this tool over siblings such as inboxAppAddMessage or updatePerson, and no prerequisites or exclusions are given.

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