Skip to main content
Glama

Vee3

by io.github.Vee3io

x-twitter.repost_post

Repost a post 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 the reposted post_id and retweeted status.

Cost = 75 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesNumeric id of the post to repost.
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
post_idNoNumeric id of the reposted post.
user_idNoNumeric X user id of the connected account.
retweetedNoWhether the post was reposted.
user_nameNoX handle of the connected account.

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/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return value ('reposted post_id and retweeted status') and cost (75 tokens), but does not mention state mutation, permissions, or potential errors. The prerequisite guidance adds some context.

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 short, purposeful sentences. It front-loads the main action, includes prerequisite and return info, and contains no fluff or redundancy.

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 output schema exists and covers return values, the description adds the prerequisite (connected_accounts) and account targeting options. It is complete for a simple repost action, though it could mention edge cases like reposting own posts or idempotency.

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 baseline is 3. The description repeats the schema's account selection logic ('Pass user_id or user_name... omit both') without adding new meaning beyond what the schema already states.

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 begins with 'Repost a post for a connected X account,' using a specific verb ('Repost') and resource ('post'). It clearly distinguishes from sibling tools like x-twitter.unrepost_post and x-twitter.create_post.

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 explicitly instructs to call x-twitter.connected_accounts first and explains how to target an account via user_id, user_name, or default. It lacks explicit exclusions or when-not-to-use alternatives, but provides clear usage context.

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