Skip to main content
Glama
Sign In
X MCP Server

X MCP Server

by siddheshutd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add-delete-bookmark

Bookmark or unbookmark a tweet by providing its ID and specifying whether to add or remove the bookmark.

Instructions

Add or delete a bookmark for a specific tweet

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": {
      "tweetId": "<tweetId>",
      "isAddBookmark": "<isAddBookmark>"
    },
    "name": "add-delete-bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
tweetIdYesThe ID of the tweet to bookmark or delete the bookmark for
isAddBookmarkYesTrue to bookmark the tweet, false to delete the bookmark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided; description lacks disclosure of side effects, permissions, error states (e.g., missing tweet), or idempotency. Only the basic operation is stated.

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?

Single sentence with no redundancy; every word contributes meaning.

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 output schema and no annotations, more detail is needed: error handling, idempotency, rate limits. The description is too minimal for safe invocation.

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 parameters are already documented. The description adds marginal value by tying isAddBookmark to add/delete, but this is implied by the parameter name.

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 clearly states the action (add or delete) and the resource (bookmark for a tweet). It distinguishes from sibling tools like like-tweet or retweet.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for choosing add vs delete despite the boolean parameter.

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