Skip to main content
Glama

Posts: React to comment

social_react_to_comment
Destructive

Like/react to one exact comment as the connected person. For a LinkedIn company page, set react_as from linkedin_list_managed_company_pages on the same account. Confirm the action and target identity. Resolve post -> comment before acting. Do not confuse post_id and comment_id. 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>",
      "reaction": "<reaction>"
    },
    "name": "social_react_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesExact provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. 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.
react_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.
reactionYesProvider-supported reaction value; LinkedIn uses linkedin_like, linkedin_celebrate, linkedin_support, linkedin_love, linkedin_insightful or linkedin_funny.
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_idYesExact comment ID belonging to the already resolved post_id. Obtain by listing comments on that post; never pass comment text or post_id here. 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. Changed2 schema fields changed
    • addedInput schema / properties / react_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"
      +}
    • changedInput schema / properties / reaction / description
      Previous value: -"Provider-supported reaction value; use the requested semantic reaction and do not invent unsupported values."New value: +"Provider-supported reaction value; LinkedIn uses linkedin_like, linkedin_celebrate, linkedin_support, linkedin_love, linkedin_insightful or linkedin_funny."
  2. Changed1 schema field changed
    • changedInput schema / properties / post_id / description
      Previous value: -"Exact provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. 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 provider post ID. Resolve/list the post first; never pass post text, author ID or a human description. 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."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety bar is lower. The description adds genuinely non-obvious context: company-page posting requires the company product enabled at account_connect plus current page admin rights, and react_as must not be used as a retry fallback after a failed company action. It omits whether a reaction can be undone and what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are valuable and front-loaded, but the trailing 'Post ID:' and 'Comment ID:' blocks duplicate the schema property descriptions almost word for word, inflating a 5-parameter tool's description with zero marginal information.

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

Completeness5/5

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

For a write tool with no output schema, the description covers identity selection, prerequisite entitlements, ID resolution chains, ordering, and the confirmation step. An agent has everything needed to invoke it correctly; only return shape and reversibility remain unstated, which the annotations partly imply.

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 coverage is 100%, so the schema already carries the per-parameter rules and the description largely repeats them verbatim ('Post ID: ... Never pass: post text...'). The one thing it adds beyond the schema is ordering ('Resolve post -> comment before acting') and the warning not to swap post_id and comment_id, which justifies keeping the baseline rather than dropping below it.

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: 'Like/react to one exact comment as the connected person.' The scope word 'comment' and the identity clause separate it from post-level or message-level reactions, but no sibling tool (e.g. linkedin_react_to_post, social_remove_comment_reaction) is named to make the boundary explicit.

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

Usage Guidelines4/5

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

Gives real procedural guidance: resolve post -> comment before acting, do not confuse post_id and comment_id, confirm the action and target identity, and use linkedin_list_managed_company_pages to populate react_as for a company page. It stops short of naming the alternative tools it replaces (react-to-post, remove-reaction), so no explicit when-not.

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.