Skip to main content
Glama

Vee3

by io.github.Vee3io

x-twitter.reply_to_post

Reply to a post from 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.

Requires reply_to_post_id. Supports the same content options as x-twitter.create_post: text, polls, media, reply settings, paid partnership disclosure, AI-generated labels, super-follower exclusivity, nullcast posts, cards, communities, and direct-message deep links.

At least one of text, poll, media, or card_uri is required, same as x-twitter.create_post.

Token pricing matches x-twitter.create_post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pollNoPoll object with options (2-4 strings) and duration_minutes (5-10080).
textNoReply text content. At least one of text, poll, media, or card_uri is required.
mediaNoFile names from files.list_uploaded_files to attach (up to 4).
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.
card_uriNoCard URI for the post. Mutually exclusive with poll and media.
nullcastNoWhether the post is promoted-only and hidden from the public timeline.
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.
community_idNoCommunity id when posting to an X community.
made_with_aiNoWhether the post contains AI-generated media.
reply_settingsNoWho can reply to the post.
paid_partnershipNoWhether the post is a paid partnership.
reply_to_post_idYesNumeric id of the post to reply to.
share_with_followersNoWhether to share a community post with followers too.
exclude_reply_user_idsNoUser ids to exclude from the reply mention list.
direct_message_deep_linkNoDeep link that moves the conversation into Direct Messages.
for_super_followers_onlyNoWhether the post is exclusive to super followers.
auto_populate_reply_metadataNoWhether to automatically populate reply metadata.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoReply text returned by the X API.
post_idNoNumeric id of the reply post.
user_idNoNumeric X user id of the connected account.
user_nameNoX handle of the connected account.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / media / description
      Previous value: -"File names from meta-tools.list_uploaded_files to attach (up to 4)."New value: +"File names from files.list_uploaded_files to attach (up to 4)."
  2. 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."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses prerequisites (connected_accounts), requirements (reply_to_post_id, at least one content type), and token pricing alignment. It doesn't cover side effects or rate limits, but the core behavior is clearly a reply creation.

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?

Five sentences, each informative: purpose, prerequisite, supported options, requirement, and token pricing. Well-structured and front-loaded.

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 17-parameter schema and output schema, the description provides essential usage context including account selection and content constraints. It references create_post for shared details, making it complete for the tool's complexity.

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?

The schema has 100% coverage with detailed per-parameter descriptions, so the baseline is 3. The description adds context by grouping content options, stating the mutual exclusivity of card_uri, and explaining account targeting logic 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?

The description uses a specific verb 'Reply to a post' and identifies the resource as a post from a connected X account. It clearly distinguishes from sibling tools like x-twitter.create_post by requiring reply_to_post_id.

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?

It instructs calling x-twitter.connected_accounts first and explains account selection via user_id/user_name or default. It references x-twitter.create_post for content options, implying the alternative for new posts, but doesn't explicitly state when not to use this tool.

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