Skip to main content
Glama
angheljf

social-media-mcp

list_x_posts

Retrieve X posts with options to limit results or filter by thread ID for social media content management.

Instructions

List X (formerly Twitter) posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of posts to return
threadIdNoID of the thread to filter by

Implementation Reference

  • The handler logic for the 'list_x_posts' tool, which filters and returns X posts.
    const { limit, threadId } = request.params.arguments;
    let filteredPosts = this.socialMediaPosts;
     if(threadId) {
        filteredPosts = filteredPosts.filter(post => post.threadId === threadId)
    }
    if(limit){
        filteredPosts = filteredPosts.slice(0, limit);
    }
    
    
    return {
        content: [{
            type: "text",
            text: JSON.stringify(filteredPosts, null, 2)
        }]
    }
  • src/index.ts:134-146 (registration)
    Registration of the 'list_x_posts' tool in the MCP server setup.
    name: "list_x_posts",
    description: "List X (formerly Twitter) posts",
    inputSchema: {
        type: "object",
        properties: {
            limit: {
                type: "number",
                description: "Maximum number of posts to return"
            },
            threadId: {
                type: "string",
                description: "ID of the thread to filter by"
            }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify critical traits: return format/structure, pagination behavior, chronological ordering, authentication requirements, or whether replies/media are included. It only states the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is extremely terse at only five words. While it avoids bloat, it is arguably underspecified rather than elegantly concise—it front-loads nothing beyond the bare minimum identifier and misses opportunities to add behavioral context in a compact way.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a social media listing tool with 2 parameters and no output schema or annotations, the description is insufficient. It fails to clarify the retrieval scope (current user? specific account? global?), the relationship between threadId and the returned dataset, or what data structure is returned.

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?

The input schema has 100% description coverage for both parameters (limit and threadId are well-described in the schema). The description adds no parameter-specific context, but with complete schema coverage, this meets the baseline expectation without requiring additional compensation from the description.

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

Purpose3/5

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

The description states the core action ('List') and resource ('X posts') and clarifies the platform with '(formerly Twitter)'. However, it lacks scope details (whose posts? timeline vs specific user?) and doesn't fully leverage the sibling differentiation opportunity, leaving gaps in understanding what exactly gets listed.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus the sibling tools (create_x_thread, post_to_x), nor when to utilize the optional threadId parameter versus retrieving unthreaded posts. The usage is only implied by the verb 'List'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/angheljf/social-media-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server