Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Truth Social post

truthsocial_post_get
Read-onlyIdempotent

Retrieve a Truth Social post by URL to read its content for research, monitoring, or analysis.

Instructions

Get a Truth Social post by URL. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Truth Social post.
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.2/5.0
Behavior2/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 fully covered by structured data. The description adds nothing beyond that: no note on external network fetch behavior, error handling for bad/unreachable URLs, or the required sequencing of conversation_id. It also says only "Requires `url`" when three parameters are in fact required, which understates the call protocol.

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 purpose and with no filler. Minor waste in the redundant "Requires `url`" clause, since the schema already marks url required and describes it as "Required."

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 single-resource fetch with no output schema, the definition covers the what but not the what-you-get: it does not characterize the returned post (fields, truncation, media handling), nor does it surface the three-parameter required contract. Adequate but with clear gaps for an open-world fetch tool.

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 (url, context, llm_model, conversation_id) are documented in the schema itself. The description only restates that url is required, adding no meaning beyond the schema. Baseline 3 applies.

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 ("Get a Truth Social post") and the lookup mechanism ("by URL"), which separates it from the profile/list siblings such as truthsocial_profile_posts_list and from other-platform post_get tools. It does not explicitly name an alternative, but the platform-qualified wording is unambiguous.

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: an agent must infer that this tool applies when it already has a Truth Social post URL rather than a profile handle or search query. There is no explicit when-to-use/when-not statement and no routing to alternatives such as truthsocial_profile_posts_list.

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