Skip to main content
Glama

LinkedIn: Reply to comment

linkedin_reply_to_comment
Destructive

Reply DIRECTLY to one exact LinkedIn comment as the connected person, or as a managed company page using comment_as from linkedin_list_managed_company_pages. Confirm the final text and target identity before publishing. Required chain from human reference: resolve post -> post.id -> list comments -> comment.id -> optionally read replies -> reply. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

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": {
      "post_id": "<post_id>",
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "linkedin_reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesFinal reply text explicitly requested/approved by the user. LinkedIn Classic mentions belong in text: @ followed by the resolved person's Classic ACo... ID or the company's numeric ID (for example @1441). Resolve people with linkedin_get_profile_from_url/linkedin_resolve_person and companies with linkedin_resolve_company/linkedin_search_companies; disambiguate every target before publishing. Never use a display name, profile URL, company slug, URN, Sales Navigator or Recruiter ID as a mention. Example after resolving both targets: 'Thanks @ACo_RESOLVED_MEMBER for working with @1441.' The API replaces each token with the target's name and mention metadata; no separate mentions field is needed. Approve the final text and mentioned identities before the write; never retry an ambiguous write automatically.
post_idYesExact post ID from post search/list. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
comment_asNoOptional numeric CompanyPage.id from linkedin_list_managed_company_pages for the SAME account_id. Choose the page by name from that list; never use mailbox_id, inbox_id, a company URL/slug, name, URN or person ID. Omit to act as the connected person. Requires the company product enabled during account_connect and current page admin rights; company search alone does not prove access. Never omit this field as a fallback after a company action fails.
comment_idYesExact comment ID from comments of the resolved post. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / comment_as
      Added value: +{
      +  "description": "Optional numeric CompanyPage.id from linkedin_list_managed_company_pages for the SAME account_id. Choose the page by name from that list; never use mailbox_id, inbox_id, a company URL/slug, name, URN or person ID. Omit to act as the connected person. Requires the company product enabled during account_connect and current page admin rights; company search alone does not prove access. Never omit this field as a fallback after a company action fails.",
      +  "pattern": "^\\d+$",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Final reply text explicitly requested/approved by the user."New value: +"Final reply text explicitly requested/approved by the user. LinkedIn Classic mentions belong in text: @ followed by the resolved person's Classic ACo... ID or the company's numeric ID (for example @1441). Resolve people with linkedin_get_profile_from_url/linkedin_resolve_person and companies with linkedin_resolve_company/linkedin_search_companies; disambiguate every target before publishing. Never use a display name, profile URL, company slug, URN, Sales Navigator or Recruiter ID as a mention. Example after resolving both targets: 'Thanks @ACo_RESOLVED_MEMBER for working with @1441.' The API replaces each token with the target's name and mention metadata; no separate mentions field is needed. Approve the final text and mentioned identities before the write; never retry an ambiguous write automatically."
  3. Changed1 schema field changed
    • changedInput schema / properties / post_id / description
      Previous value: -"Exact post ID from post search/list. Post ID: Exact provider/Unipile post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."New value: +"Exact post ID from post search/list. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description goes further by requiring confirmation of final text and target identity before publishing and by warning never to auto-retry an ambiguous write. It also discloses the admin/product prerequisites for posting as a company page. It does not describe the response body, which is the remaining gap.

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?

Front-loaded with the action and actor, then the chain, then per-ID rules. It is somewhat long and duplicates schema field text, but nearly every sentence carries an actionable constraint rather than filler.

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?

For a 5-parameter, non-idempotent write with no output schema, the description covers identity, mention-token rules, ID provenance and prerequisites thoroughly. Only the shape of the publish response and failure modes are left unstated.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents each field in depth, so the description's ID-targeting paragraphs largely restate it. It still adds usable rules the schema text does not emphasize as a whole — the negative constraints 'Never pass: post text, author user ID, URL' and the ordering of the resolution chain across post_id and comment_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (reply) plus resource (one exact LinkedIn comment) with actor scope (connected person or managed company page). The word 'DIRECTLY to one exact comment' distinguishes it from linkedin_comment_on_post and from linkedin_list_comment_replies without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit resolution chain (resolve post -> post.id -> list comments -> comment.id) and names which sibling tools supply each ID. It also states when to use comment_as and warns against using it as a fallback after a company action fails.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.