Narrareach

List LinkedIn destinations

list_linkedin_destinations

Destructive

Refresh and list LinkedIn personal profiles and Company Pages available for Notes. Returns accountId, organizationUrn for Pages, and the configured default destination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_linkedin_destinations"
  }
}

Input Schema

Name	Required	Description	Default
`writer`	No	Optional team writer name, handle, or id within the authorized workspace.
`workspace`	No	Optional authorized team workspace name or id.

Output Schema

Name	Required	Description	Default
`context`	Yes
`destinations`	Yes
`connectedAccount`	No
`defaultDestination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

changedOutput schema / properties / defaultDestination / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "accountId": {
-        "type": "string"
-      },
-      "isDefault": {
-        "type": "boolean"
-      },
-      "kind": {
-        "enum": [
-          "profile",
-          "page"
-        ],
-        "type": "string"
-      },
-      "label": {
-        "type": "string"
-      },
-      "organizationUrn": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "accountId",
-      "label",
-      "kind",
-      "isDefault"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "accountId": {
+        "type": "string"
+      },
+      "aliasAccountIds": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "isDefault": {
+        "type": "boolean"
+      },
+      "kind": {
+        "enum": [
+          "profile",
+          "page"
+        ],
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "organizationUrn": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "accountId",
+      "label",
+      "kind",
+      "isDefault"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / destinations / items / properties / aliasAccountIds
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

First observedOct 1, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, and the description's 'Refresh' wording is consistent with a non-read-only operation. It also adds useful return context (accountId, organizationUrn, default destination). However, the surprising destructiveHint=true for a list-style tool is never explained, nor are auth/workspace requirements.

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, zero filler, with the scope and the return payload front-loaded. Nothing in the text is redundant or wasteful.

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?

An output schema exists, so return fields need not be restated, yet the description is otherwise thin on behavior for a tool whose annotations flag it as destructive and non-idempotent. The unexplained destructive hint leaves a real gap for an agent deciding whether to call it.

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 the optional writer and workspace parameters are already documented in the schema. The description adds nothing about these parameters, which is acceptable given the schema coverage but yields only the baseline.

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?

States a specific verb pair (refresh and list) and resource (LinkedIn personal profiles and Company Pages), and scopes it with 'available for Notes', which implicitly separates it from list_linkedin_article_destinations. It does not name any sibling explicitly, so it stops short of a 5.

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 reference to the nearest alternatives (list_linkedin_article_destinations, list_social_accounts). An agent must infer that this is the pre-scheduling lookup for LinkedIn notes rather than being told.

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

All Narrareach tools Inspect

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

Need Help?