Skip to main content
Glama
TwitterAPIs

twitterapis

by TwitterAPIs

twitter_bookmark_tweet

Add a tweet to your private bookmarks by providing its ID or URL.

Instructions

Bookmark a tweet to YOUR authenticated account's private bookmarks. Provide the tweet id or url. Requires write capability behind your key. Reverse with twitter_unbookmark_tweet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTweet/post numeric id (e.g. "1789012345678901234"). Provide exactly one of id or url.
ct0NoOptional. The account's ct0 cookie, paired with auth_token. Sent as the x-ct0 header.
urlNoFull tweet URL, e.g. "https://x.com/elonmusk/status/1789012345678901234". Provide exactly one of id or url.
accountNoOptional. The @handle (without @) of the authenticated account to act AS, when your key manages more than one session. Omit to use your key's default session.
proxy_urlNoOptional. Residential proxy URL to egress this call through. Recommended for writes: X soft-blocks writes from datacenter IPs as automated. Sent as the x-proxy-url header.
auth_tokenNoOptional. The account's auth_token cookie, to act AS that account for this call (must be paired with ct0). Sent as the x-auth-token header; never placed in the URL.
user_agentNoOptional. User-Agent string to send for this session. Sent as the x-user-agent header.
Behavior4/5

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

Description adds behavioral context beyond annotations: it clarifies the action is for the authenticated account's private bookmarks, requires write capability, and is reversible via the sibling tool. No contradictions with annotations.

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 two sentences, front-loaded with the core purpose, and every word adds value. It is highly concise and well-structured.

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?

Given the tool's simplicity, the description covers the essential action, authentication requirement, and input guidance. No output schema exists, but the open-world hint annotations account for variable responses. Missing details like success indicators or error cases, but it is reasonably complete for a bookmark action.

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 description does not need to add parameter details. It merely reinforces that the user should provide 'tweet id or url,' which is already in the schema. No additional semantic value beyond the schema.

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?

Description clearly states the action: 'Bookmark a tweet to YOUR authenticated account's private bookmarks.' It specifies the verb 'Bookmark' and the resource 'tweet', and distinguishes from sibling 'twitter_unbookmark_tweet' by mentioning the reverse action.

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?

The description explicitly notes 'Requires write capability behind your key' and mentions the reverse action, providing clear context for when to use this tool. It lacks explicit when-not-to-use or alternatives beyond the reverse, but it is sufficient for a simple write operation.

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/TwitterAPIs/twitterapis-mcp'

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