Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

inboxAppGetParticipants

Retrieve participants of an inbox app conversation using the inbox app ID and external conversation ID.

Instructions

List participants of an inbox app conversation.

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

Input Schema

NameRequiredDescriptionDefault
inboxAppIdYesID of the inbox app making the call.
extConversationIdYesYour external ID of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedInput schema / properties / conversationId
      Removed value: -{
      -  "description": "Conversation ID",
      -  "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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "conversationId"
      -]New value: +[
      +  "inboxAppId",
      +  "extConversationId"
      +]
  2. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only supply default-style hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false) and the description adds nothing beyond them — no note on permissions required to read a conversation, ordering of returned participants, or pagination/limit behavior. There is a mild tension worth flagging to callers: a 'list/get participants' operation is intuitively a read, yet readOnlyHint is false, and the description never clarifies the discrepancy.

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?

A single front-loaded sentence with zero filler, which is structurally sound. It is arguably under-sized rather than over-sized, but that gap is captured under contextual completeness rather than conciseness.

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?

With no output schema, the description carries the full burden of telling the agent what comes back (participant shape, empty-list behavior) and it says nothing about return values, ordering, or limits. For a small two-parameter lookup this is a real gap — an agent cannot predict whether the response is a bare array or a wrapped object.

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 both parameters (inboxAppId, extConversationId) are already documented in the schema itself. The description adds no meaning beyond that — it does not explain what 'extConversationId' must correspond to (e.g., the conversation ID returned by inboxAppAddMessage) or whether the inbox app ID must match the install. Baseline 3 is appropriate.

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?

"List participants of an inbox app conversation" gives a clear verb (list) and resource (participants scoped to a conversation), so an agent can tell this apart from inboxAppCreateParticipant or inboxAppUpdateConversation by the read-oriented 'list' verb. It falls short of a 5 because it does not explicitly position itself against those siblings or state scope limits (e.g., all participants vs. paginated subset).

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 guidance, no prerequisites, and no mention of the obvious alternative sibling (inboxAppCreateParticipant) or what to do if the conversation ID is unknown. The agent must infer usage entirely from the tool name and the two required parameters.

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