Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Truth Social profile

truthsocial_profile_get
Read-onlyIdempotent

Retrieve a Truth Social profile by handle or account ID to view account details for a specified user.

Instructions

Get a Truth Social profile by handle or account id. Requires handle.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no auth requirements, no rate limits, no note that upstream data may be unavailable or private, and no hint about the conversation_id handshake protocol.

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, no filler, and the resource and identifier form are front-loaded. Nothing in the text is redundant with itself.

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 simple read tool with no output schema, the description is minimally sufficient, and the schema fully documents the three required parameters. However, the conversation_id echo rule and the prohibition on parallel calls are operationally critical and live only in the schema, so an agent skimming the description alone could invoke this tool incorrectly.

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 all four parameters—including the unusual context, llm_model, and conversation_id fields—are documented in the schema itself. The description merely repeats that handle is required and adds no format or identifier-resolution detail beyond it, which is the expected baseline when the schema does the work.

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 ("Get a Truth Social profile") plus the two accepted identifier forms (handle or account id), which cleanly separates it from truthsocial_profile_posts_list and truthsocial_post_get. It never names those siblings explicitly, so the differentiation is implicit rather than stated.

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 when-to-use guidance, no exclusions, and no mention of the alternative siblings for retrieving activity vs. profile data. The only guidance ("Requires handle") is a restatement of the schema's required field rather than a usage condition, and nothing warns about the sequencing constraint on conversation_id.

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