Skip to main content
Glama
XcrapCC

@xcrap/mcp

Official
by XcrapCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Export an X account's posts

xcrap_get_user_history
Read-onlyIdempotent

Fetch an account's entire post history in one call, paginating the timeline automatically and optionally filtering by date range. Get all posts with timestamps and metrics for summaries or analysis.

Instructions

Fetch many of an account's posts in one call — walking its timeline page by page — optionally limited to a date window.

This is for "everything @x posted in March", "their last 200 posts" or "summarise what they said about Y this year". It replaces paging xcrap_get_user_tweets yourself, and it counts as one call against its budget however many pages it walks.

When to use this instead of the alternatives:

  • Use xcrap_get_user_tweets for a quick look at the latest posts.

  • Use xcrap_get_thread for one connected chain of posts.

Args:

  • handle (string, required): "jack", "@jack" or a profile URL.

  • max_posts (number, 1-200): stop after this many posts, default 50. The API allows up to 1,000, but a result that large will not fit in a context window; narrow the dates instead.

  • since (string): oldest post to include, as a date such as "2025-01-01".

  • until (string): newest post to include, as a date.

  • include_replies (boolean): default false. Set true to include the account's replies to other people.

Returns markdown: a "Post history" heading with the count and the window, then every post with its timestamp, permalink, text and metrics.

Costs 5 calls per 5 minutes — it is the most expensive tool here, so choose the window before calling rather than calling repeatedly. It takes about a second per twenty posts, and the further back a window sits, the patchier X's timeline is — an old window can legitimately come back empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoOldest post to include, as a date: "2025-01-01" or an ISO timestamp.
untilNoNewest post to include, as a date: "2025-03-31" or an ISO timestamp.
handleYesX handle, @handle or profile URL whose posts to export.
max_postsNoStop after this many posts, 1-200 (default 50). Narrow since/until rather than raising this.
include_repliesNoInclude the account's replies to other people (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, but the description adds significant behavioral context: it counts as one call against budget regardless of pages walked, costs 5 calls per 5 minutes (the most expensive), performance (~1 sec per 20 posts), and the risk of empty results for old windows due to X's timeline patchiness. It also discloses the markdown return format, which is not in an output schema. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, when-to-use, args, returns, cost) and front-loads the core purpose. It is slightly verbose—particularly the cost and performance details—but every sentence adds operational value. No fluff, though a few sentences could be trimmed without loss.

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?

For a tool that walks pages, has a date window, and a cost budget, the description covers everything an agent needs: purpose, usage scenarios, argument semantics, return format, cost, performance, and data-completeness caveats. No output schema exists, so the description appropriately explains the markdown structure. There are no missing critical details.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema: it explains the context-window limitation for max_posts ('The API allows up to 1,000, but a result that large will not fit in a context window; narrow the dates instead') and reinforces the recommended approach of narrowing dates rather than raising max_posts. It also clarifies handle accepts '@jack' or profile URLs. This extra guidance pushes it above the baseline.

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 opens with a specific verb and resource ('Fetch many of an account's posts in one call — walking its timeline page by page'), and immediately distinguishes itself from siblings by explaining it replaces manual paging of xcrap_get_user_tweets. It names the alternatives (xcrap_get_user_tweets, xcrap_get_thread) with their appropriate use cases, so an agent can disambiguate without inspecting other schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use examples are given ('everything @x posted in March', 'their last 200 posts') alongside explicit alternatives: 'Use xcrap_get_user_tweets for a quick look at the latest posts' and 'Use xcrap_get_thread for one connected chain of posts.' This leaves no ambiguity about when to select this tool over its siblings.

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

Deploy Server

Other Tools