Skip to main content
Glama

XCROP X (Twitter) data

Get posts of an account

get_user_tweets
Read-only

Latest posts of an X account (its Posts tab). Costs 15 credits per post returned.

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": {
      "username": "<username>"
    },
    "name": "get_user_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many posts to return (default 10, max 100)
cursorNonext_cursor from the previous page, to continue
usernameYesX username without @, e.g. elonmusk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds two things annotations do not carry: a concrete cost model ('15 credits per post returned') and the scoping hint that results come from the account's Posts tab. It stops short of describing auth requirements or what a returned post contains.

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?

Two short sentences with no filler. The scope statement comes first and the cost caveat second, so the agent sees the purpose before the billing implication.

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?

For a three-parameter read tool with no output schema, the definition covers purpose, scope, and cost, which are the decision-relevant facts. The remaining gap is that return shape is never described and, with no output schema present, the description was the only place it could have been stated.

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% and all three parameters are documented in the schema, including defaults, min/max, and the meaning of next_cursor. The description adds only indirect meaning via the per-post cost, which implies count drives spend; baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Latest posts of an X account', and the parenthetical '(its Posts tab)' narrows the resource to a particular content type. It never names a sibling such as search_tweets or get_tweet_replies, so an agent must infer the boundary itself, which keeps this short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the 'Posts tab' phrasing hints that this returns timeline posts rather than search results or replies, but there is no explicit when-to-use or when-not-to-use statement and no alternative is named. For a tool that sits alongside search_tweets and get_user, that routing guidance is genuinely absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources