Skip to main content
Glama
Sign In
x-mcp

x-mcp

by EL4CTEO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

X engagement

x_engagement
Idempotent

Like, repost, bookmark posts, or undo those actions as the authenticated account.

Instructions

Like, repost and bookmark posts, and undo those actions, as the authenticated account.

Actions (pass "action" plus that action's parameters):

  • like: Like a post as the authenticated account. [requires: tweet_id]

  • unlike: Remove a like from a post. [requires: tweet_id]

  • repost: Repost a post to your followers. [requires: tweet_id]

  • unrepost: Remove one of your reposts. [requires: tweet_id]

  • bookmark: Save a post to your bookmarks. [requires: tweet_id]

  • unbookmark: Remove a post from your bookmarks. [requires: tweet_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": {
      "action": "<action>"
    },
    "name": "x_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform. One of: like, unlike, repost, unrepost, bookmark, unbookmark.
tweet_idNoNumeric post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, idempotent, non-destructive, open-world tool. The description adds useful context that actions are performed as the authenticated account and that undo variants exist, but it does not cover rate limits, authentication failure behavior, or visibility effects beyond what annotations provide.

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 front-loaded with the core purpose and then structured as an efficient action-by-action list. Each line earns its place by naming the action and its required parameter.

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 two-parameter action tool with complete schema coverage and annotations covering safety traits, the description is complete enough to select and invoke actions correctly. A minor gap remains around error behavior and rate-limit context, but no output schema exists so return values need not be explained.

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%, so the enum and tweet_id description already carry most parameter meaning. The description adds value by making explicit that every listed action requires tweet_id, which is not expressed by the schema's top-level required list that only requires action.

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?

The description gives specific verbs and resources: like, repost, bookmark, and undo those actions on posts as the authenticated account. The enumerated action list makes the tool's engagement scope distinct from sibling tools such as x_posts, x_users, and x_timelines.

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

Usage Guidelines3/5

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

The description explains how to select an action and which parameter that action needs, but it does not explicitly say when to use this tool instead of sibling tools or when not to use it. Usage is implied by the action list rather than stated as routing guidance.

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

Deploy Server

Other Tools