Skip to main content
Glama

Vee3

by io.github.Vee3io

x-twitter.get_bookmarks

Fetch bookmarked posts for a connected X account.

Call x-twitter.connected_accounts first. Pass user_id or user_name to target a specific account, or omit both to use the default account.

Returns raw X API data with tweet objects, expanded authors, media, polls, and places. Use next_cursor to fetch the next page.

Cost = 25 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of bookmarks to return (default 20, max 100).
cursorNoPagination cursor from a previous response next_cursor field.
user_idNoNumeric X user id from x-twitter.connected_accounts. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account.
user_nameNoX handle from x-twitter.connected_accounts, with or without a leading @. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoBookmarked posts returned by the X API.
includesNoExpanded users, media, polls, places, and referenced posts.
next_cursorNoCursor for the next page of bookmarks, when available.
result_countNoNumber of bookmarks in this page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / user_id / description
      Previous value: -"Numeric X user id from get-x-connected-accounts. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account."New value: +"Numeric X user id from x-twitter.connected_accounts. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account."
    • changedInput schema / properties / user_name / description
      Previous value: -"X handle from get-x-connected-accounts, with or without a leading @. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account."New value: +"X handle from x-twitter.connected_accounts, with or without a leading @. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses return format (raw X API data, tweet objects, expanded authors, media, polls, places), pagination via next_cursor, cost (25 tokens), and the prerequisite of calling x-twitter.connected_accounts. This is solid but doesn't mention rate limits or error conditions.

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 four sentences, each serving a purpose: purpose, prerequisite/targeting, return format/pagination, and cost. It is front-loaded with the core purpose and is free of fluff.

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?

Given the output schema tracks returns and the parameter schema covers details, the description adds necessary context: prerequisite, targeting, pagination, and cost. It is complete for a read-only fetch tool with no required parameters.

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% with all parameters described. The description reinforces the user_id/user_name relationship and mentions pagination, but it already exists in the schema. It adds minimal new semantic value beyond emphasizing the default-account behavior.

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 tool fetches bookmarked posts for a connected X account, using a specific verb ('Fetch') and resource ('bookmarked posts'). It is distinct from sibling tools like create_bookmark, delete_bookmark, and search, and the purpose is unambiguous.

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 provides clear usage context: call x-twitter.connected_accounts first, and either pass user_id/user_name or omit both to use the default account. While it doesn't explicitly contrast with alternative tools, it gives a prerequisite and targeting guidance sufficient for most use cases.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources