KonbiniAPI MCP

LinkedIn: Get user articles

linkedin_get_user_articles

Read-onlyIdempotent

Returns a public LinkedIn member's published articles. This endpoint is not paginated — everything available is returned in a single response. Supports projection_preset, data_fields, and item_fields for payload reduction.

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": {
      "username": "<username>"
    },
    "name": "linkedin_get_user_articles"
  }
}

Input Schema

Name	Required	Description
`username`	Yes	LinkedIn username
`data_fields`	No	Optional. Add top-level data keys on top of the selected projection_preset.
`item_fields`	No	Optional. Add item keys from data.orderedItems[] on top of the selected projection_preset.
`projection_preset`	No	Optional. Defaults to "minimal". Use one of: full, minimal, identity, engagement, or content.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / item_fields / items / enum

Previous value: -[
-  "type",
-  "url",
-  "name",
-  "image",
-  "likeCount",
-  "attributedTo"
-]New value: +[
+  "type",
+  "url",
+  "name",
+  "image",
+  "published",
+  "likeCount",
+  "attributedTo"
+]

AddedSep 10, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the endpoint is not paginated and returns all available items in one response, and the projection parameters exist for payload reduction. It does not describe error cases or rate limits.

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?

Three sentences, front-loaded with the core purpose, then the pagination trait, then the projection knobs. No filler, though the last sentence largely restates functionality the schema already exposes.

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?

No output schema exists, but the description conveys the response shape indirectly by stating everything is returned in one unpaginated response and that payload size is controllable via projections. Missing only a brief note on what an item represents or error behavior.

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 the schema already documents username and the projection/data_fields/item_fields parameters in detail, including the 'minimal' default. The description names the reduction parameters and their purpose but adds no syntax or semantics beyond the schema, so 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?

States a specific verb and resource: returns a public LinkedIn member's published articles. The 'articles' vs 'posts' distinction implicitly separates it from linkedin_get_user_posts, though no sibling is named. An agent can identify the resource without opening the schema.

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 explicit when-to-use guidance or mention of alternatives such as linkedin_get_user_posts or linkedin_get_user. Usage is only implied by the tool name and the statement that the endpoint is unpaginated.

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

All KonbiniAPI MCP 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?