Narrareach

List LinkedIn Article destinations

list_linkedin_article_destinations

Destructive

List personal profiles and Company Pages available for LinkedIn Articles. With authorUrn, also returns newsletters owned by that author.

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_article_destinations"
  }
}

Input Schema

Name	Required	Description	Default
`refresh`	No	Refresh verified destinations from LinkedIn instead of reusing the recent session-bound list.
`authorUrn`	No	Optional author URN returned by this tool. When supplied, Narrareach also returns newsletters owned by that profile or Page.

Output Schema

Name	Required	Description	Default
`authors`	Yes
`warning`	No
`newsletters`	Yes
`connectedAccount`	No
`pageRefreshFailed`	No
`articleSessionActive`	No
`usingSavedDestinations`	No
`newsletterRefreshFailed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description frames the tool as a plain enumeration and never explains what is destructive or mutated (the refresh parameter's cache/session side effect is the only hint). The description does add the conditional authorUrn behavior, but the safety-relevant behavior implied by the annotations is left unexplained.

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 tight sentences, zero filler, with the base behavior front-loaded and the conditional authorUrn branch second. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full input schema and an output schema present, the description does not need to describe return values; it correctly limits itself to scope plus the authorUrn branch. The remaining gap is routing context — no comparison against the sibling destination-listing tool and no reconciliation of the destructive annotation.

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% and both parameters are fully documented there, including the authorUrn newsletter behavior that the description merely restates. The description adds no syntax, defaults, or edge-case semantics beyond the schema, so the baseline 3 applies.

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 pairs a specific verb ('List') with a specific resource ('personal profiles and Company Pages available for LinkedIn Articles') and adds the conditional newsletter behavior. An agent knows exactly what comes back. It stops short of a 5 because it never names the closely related sibling list_linkedin_destinations, so the distinction between 'all destinations' and 'destinations valid for Articles' must be inferred from the scope phrase alone.

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?

The scope phrase 'available for LinkedIn Articles' weakly implies the calling context (picking a destination when publishing an article), but there is no explicit when-to-use, no prerequisites, and no mention of the alternative list_linkedin_destinations. An agent must guess which of the two list tools to call.

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?