Skip to main content
Glama
Linked-API
by Linked-API

react_to_post

Add reactions to LinkedIn posts using available types like like, love, support, celebrate, insightful, or funny to engage with content.

Instructions

Allows you to react to a post using any available reaction type (st.reactToPost action).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postUrlYesLinkedIn URL of the post to react. (e.g., 'https://www.linkedin.com/posts/username_activity-id')
typeYesEnum describing the reaction type.

Implementation Reference

  • ReactToPostTool class: defines the tool name 'react_to_post', LinkedIn operation name, Zod validation schema, and MCP Tool object with inputSchema. Inherits execution logic from OperationTool.
    export class ReactToPostTool extends OperationTool<TReactToPostParams, unknown> {
      public override readonly name = 'react_to_post';
      public override readonly operationName = OPERATION_NAME.reactToPost;
      protected override readonly schema = z.object({
        postUrl: z.string(),
        type: z.enum(['like', 'love', 'celebrate', 'support', 'funny', 'insightful']).or(z.string()),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to react to a post using any available reaction type (st.reactToPost action).',
          inputSchema: {
            type: 'object',
            properties: {
              postUrl: {
                type: 'string',
                description:
                  "LinkedIn URL of the post to react. (e.g., 'https://www.linkedin.com/posts/username_activity-id')",
              },
              type: {
                type: 'string',
                description: 'Enum describing the reaction type.',
                enum: ['like', 'love', 'support', 'celebrate', 'insightful', 'funny'],
              },
            },
            required: ['postUrl', 'type'],
          },
        };
      }
    }
  • Execute method in OperationTool (base class for ReactToPostTool): finds the LinkedAPI operation matching 'reactToPost' and executes it with input args and progress reporting.
    public override execute({
      linkedapi,
      args,
      workflowTimeout,
      progressToken,
    }: {
      linkedapi: LinkedApi;
      args: TParams;
      workflowTimeout: number;
      progressToken?: string | number;
    }): Promise<TMappedResponse<TResult>> {
      const operation = linkedapi.operations.find(
        (operation) => operation.operationName === this.operationName,
      )! as Operation<TParams, TResult>;
      return executeWithProgress(this.progressCallback, operation, workflowTimeout, {
        params: args,
        progressToken,
      });
    }
  • Zod schema for validating react_to_post input parameters: postUrl (string) and type (reaction enum or string).
    protected override readonly schema = z.object({
      postUrl: z.string(),
      type: z.enum(['like', 'love', 'celebrate', 'support', 'funny', 'insightful']).or(z.string()),
    });
  • Instantiation of ReactToPostTool within the LinkedApiTools constructor's tools array, registering it for use in the MCP server.
    new ReactToPostTool(progressCallback),
  • Initialization of LinkedApiTools in LinkedApiServer, which includes the react_to_post tool among others, for provision to the MCP server.
    this.tools = new LinkedApiTools(progressCallback);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'allows you to react' which implies a write/mutation operation, but doesn't disclose important behavioral aspects: whether this requires authentication, if there are rate limits, whether reactions are reversible, what happens if the post doesn't exist, or what the response looks like. The description adds minimal behavioral context beyond the basic action.

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?

The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple action tool and front-loads the essential information. Every word earns its place.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address authentication requirements, error conditions, response format, or practical usage considerations. While the schema covers parameters well, the overall context for using this tool safely and effectively is lacking.

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 fully documents both parameters (postUrl with format example, type with enum values). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain reaction type implications, URL validation rules, or parameter interactions. Baseline 3 is appropriate when schema does all the documentation work.

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 clearly states the action ('react to a post') and resource ('post'), and specifies it uses 'any available reaction type'. It distinguishes from obvious siblings like 'comment_on_post' by focusing on reactions rather than comments. However, it doesn't explicitly differentiate from all possible sibling tools in the list.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to react versus comment, or whether reactions are appropriate for different post types. No prerequisites, exclusions, or comparison to sibling tools are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Linked-API/linkedapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server