Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Threads post

threads_post_get
Read-onlyIdempotent

Retrieve a single Threads post by URL to view its content and details, with an option to return a smaller response containing fewer fields.

Instructions

Get a single Threads 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": "threads_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the Threads post.
trimNoWhen true, returns a smaller response with fewer fields.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that — it does not mention that the response may be trimmed, that a conversation_id handshake is expected before parallel calls, or any auth/rate-limit behavior.

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, front-loaded sentences with no padding or narrative clutter. The second sentence is somewhat wasted since it repeats a requirement already declared in the schema.

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?

No output schema exists, so the description should carry return-value expectations (e.g. what a trimmed vs. full post looks like), but it says nothing. It also omits the multi-step conversation_id protocol implied by the required parameters, which is material to calling this tool correctly.

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 including trim, context, llm_model, and conversation_id is documented in the schema itself. The description's only parameter remark ('Requires `url`') merely restates the schema's required field, adding no format or URL-syntax guidance, so the 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 and resource ('Get a single Threads post') and the input form ('by URL'), which pins the operation down precisely. It does not differentiate from the many sibling retrieval tools (mastodon_post_get, reddit_post_get, threads_profile_posts_list), relying on the name's platform prefix to do that work.

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?

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as threads_profile_posts_list for enumerating posts or other platform post_get tools. Usage is only implied by the verb 'Get'.

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