Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Truth Social profile posts

truthsocial_profile_posts_list
Read-onlyIdempotent

List posts from a Truth Social profile using a handle or account ID, with cursor pagination and optional replies for timeline analysis.

Instructions

List posts from a Truth Social profile by handle or account id. Requires handle. Returns a list (use cursor when paginated).

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "truthsocial_profile_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum posts to return (1–20). Default: 20.
cursorNoOpaque pagination cursor from a previous response. Omit for the first page.
handleYesRequired. Truth Social handle or account id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
includeRepliesNoWhen true, includes reply posts in the timeline. Adds 2 credits (4 total including the base lookup). Default: false (top-level posts only).
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are a list and that pagination uses a cursor, but it omits notable behavior such as the credit cost of includeReplies and the conversation_id echo requirement, both of which live only in the schema.

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?

Two short sentences, front-loaded with the core action and the required key. "Requires `handle`" mildly duplicates the schema's own required marker, but there is no padding or wasted prose.

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

Completeness3/5

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

For a 7-parameter tool with no output schema, the description covers the essential shape (list, cursor pagination, required handle) but leaves the agent to discover the conversation_id sequencing rule and credit implications from the schema alone. Adequate but not fully self-sufficient.

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 description coverage is 100%, so every parameter is already documented in the input schema, including limit bounds, cursor semantics, and the credit note on includeReplies. The description adds no meaning beyond that, which is the expected baseline of 3 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 and resource ("List posts from a Truth Social profile") and names the lookup key (handle or account id), which separates it from truthsocial_profile_get and truthsocial_post_get. It stops short of explicitly contrasting with those siblings, so it lands at 4 rather than 5.

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?

The only usage guidance is "use cursor when paginated," which is a mechanical hint rather than a when-to-use rule. There is no statement of when to prefer this over truthsocial_profile_get or the other network-specific posts_list siblings, and no exclusions.

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