Skip to main content
Glama
Sign In

Inboxapp

by com.inboxapp.mcp
OverviewDiscussionsAdmin

Send connection request

relationships_connect

Send connection request

Invites a profile to connect with the account link. Needs profile:connect.

Input Schema

NameRequiredDescriptionDefault
noteNo
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / Platform / description
      Previous value: -"The platform. Every team can use twitter, linkedin; a team may have others enabled."New value: +"The platform. Every team can use twitter, linkedin, whatsapp; a team may have others enabled."
    • changedInput schema / $defs / Platform / examples
      Previous value: -[
-  "twitter",
-  "linkedin"
-]New value: +[
+  "twitter",
+  "linkedin",
+  "whatsapp"
+]
  2. Changed2 schema fields changed
    • changedInput schema / $defs / Platform / description
      Previous value: -"The platform. Every team can use twitter; a team may have others enabled."New value: +"The platform. Every team can use twitter, linkedin; a team may have others enabled."
    • changedInput schema / $defs / Platform / examples
      Previous value: -[
-  "twitter"
-]New value: +[
+  "twitter",
+  "linkedin"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / target / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "The profile of an existing one-to-one thread, from the thread's account link.",
-    "properties": {
-      "threadId": {
-        "$ref": "#/$defs/Cuid2"
-      },
-      "type": {
-        "enum": [
-          "thread"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "threadId"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "The contact's profile on the account link's platform. Fails with `recipientUnavailable` when the contact has none there, and `profileAmbiguous` when it has several.",
-    "properties": {
-      "accountLinkId": {
-        "allOf": [
-          {
-            "$ref": "#/$defs/Cuid2"
-          },
-          {
-            "description": "The account link to send the request from."
-          }
-        ]
-      },
-      "contactId": {
-        "$ref": "#/$defs/Cuid2"
-      },
-      "type": {
-        "enum": [
-          "contact"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "accountLinkId",
-      "contactId"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "A platform user. Without the Advanced API add-on, the profile must already belong to one of the team's contacts.",
-    "properties": {
-      "accountLinkId": {
-        "allOf": [
-          {
-            "$ref": "#/$defs/Cuid2"
-          },
-          {
-            "description": "The account link to send the request from."
-          }
-        ]
-      },
-      "platform": {
-        "allOf": [
-          {
-            "$ref": "#/$defs/Platform"
-          },
-          {
-            "description": "Must be the account link's platform."
-          }
-        ]
-      },
-      "platformId": {
-        "description": "The ID the platform gives this object. Only meaningful next to its `platform`.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "profile"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "accountLinkId",
-      "platform",
-      "platformId"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "The profile of an existing one-to-one thread, from the thread's account link.",
+    "properties": {
+      "threadId": {
+        "$ref": "#/$defs/Cuid2"
+      },
+      "type": {
+        "enum": [
+          "thread"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "threadId"
+    ],
+    "title": "Thread",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "The contact's profile on the account link's platform. Fails with `recipientUnavailable` when the contact has none there, and `profileAmbiguous` when it has several.",
+    "properties": {
+      "accountLinkId": {
+        "allOf": [
+          {
+            "$ref": "#/$defs/Cuid2"
+          },
+          {
+            "description": "The account link to send the request from."
+          }
+        ]
+      },
+      "contactId": {
+        "$ref": "#/$defs/Cuid2"
+      },
+      "type": {
+        "enum": [
+          "contact"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "accountLinkId",
+      "contactId"
+    ],
+    "title": "Contact",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "A platform user. Without the Advanced API add-on, the profile must already belong to one of the team's contacts.",
+    "properties": {
+      "accountLinkId": {
+        "allOf": [
+          {
+            "$ref": "#/$defs/Cuid2"
+          },
+          {
+            "description": "The account link to send the request from."
+          }
+        ]
+      },
+      "platform": {
+        "allOf": [
+          {
+            "$ref": "#/$defs/Platform"
+          },
+          {
+            "description": "Must be the account link's platform."
+          }
+        ]
+      },
+      "platformId": {
+        "description": "The person's ID on the platform. Reaching someone Inboxapp hasn't stored needs the account link's `profile:resolve:id`.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "profile"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "accountLinkId",
+      "platform",
+      "platformId"
+    ],
+    "title": "Profile by platform ID",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "A platform user. Without the Advanced API add-on, the profile must already belong to one of the team's contacts.",
+    "properties": {
+      "accountLinkId": {
+        "allOf": [
+          {
+            "$ref": "#/$defs/Cuid2"
+          },
+          {
+            "description": "The account link to send the request from."
+          }
+        ]
+      },
+      "platform": {
+        "allOf": [
+          {
+            "$ref": "#/$defs/Platform"
+          },
+          {
+            "description": "Must be the account link's platform."
+          }
+        ]
+      },
+      "type": {
+        "enum": [
+          "profile"
+        ],
+        "type": "string"
+      },
+      "username": {
+        "description": "The person's username on the platform, without a display prefix such as `@`. On LinkedIn, what follows `/in/` in their profile URL: the vanity name or the `ACoA…` profile ID. Reaching someone Inboxapp hasn't stored needs the account link's `profile:resolve:username`.",
+        "examples": [
+          "jane",
+          "ACoAABcdEfGh1234567890"
+        ],
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "accountLinkId",
+      "platform",
+      "username"
+    ],
+    "title": "Profile by username",
+    "type": "object"
+  }
+]
  4. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-idempotent, open-world operation that is not destructive, so the safety profile is covered. The description adds the `profile:connect` permission requirement, which is genuinely useful, but says nothing about what happens on success, whether repeat calls duplicate requests, or failure modes such as already-connected or note exhaustion.

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?

Very short and front-loaded, with the action first and the permission requirement second. The only waste is the redundant restatement of the title 'Send connection request' as the opening line.

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 mutation tool with no output schema and a complex polymorphic `target`, the description covers only the permission gate. An agent can call it, but must read the schema to know which target form to supply and has no stated expectation of the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Reported schema description coverage is 0%, so the description is expected to compensate, yet it never mentions the `target` union or the optional `note`. It does not explain the four target shapes (thread, contact, profile by ID, profile by username) or their differing requirements.

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 ('Invites a profile to connect with the account link'), which is clearly distinct from message-sending siblings like messages_send. It stops short of naming or contrasting any sibling, so an agent gets the action but not explicit differentiation.

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?

No when-to-use, when-not-to-use, or alternative is given; an agent must infer that this is for outreach rather than messaging. The only guidance is the permission requirement, which is a prerequisite rather than a usage rule.

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

All Inboxapp toolsInspect
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.

Resources