Skip to main content
Glama
Threads MCP

Threads MCP

by kerwilgil

Get Threads post

threads_get_post
Read-onlyIdempotent

Fetches a single Threads post by provider post ID so you can verify its content and details.

Instructions

Fetch one Threads post by provider post id for verification.

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": {
      "post_id": "<post_id>"
    },
    "name": "threads_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
textNo
media_urlNo
permalinkNo
timestampNo
media_typeNo
thumbnail_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds only that the id is a provider id and the fetch is for verification; it says nothing about behavior when the post is missing or inaccessible, or about auth/visibility constraints inherent to an open-world call.

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?

One short sentence with the verb and lookup key front-loaded and no filler. It is efficient but at the edge of under-specification rather than maximally informative.

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?

With an output schema present the return shape needn't be described, and annotations cover safety, so the remaining burden is small. Still, for an open-world fetch the definition omits what happens on not-found/private posts and any id-format expectation, leaving minor gaps for a simplicity-level 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?

The single parameter has 0% schema description coverage, so the description must carry the load; calling it a 'provider post id' usefully signals the identifier namespace (Threads/provider-side rather than an internal handle). It still gives no format example, so the meaning is clarified but not fully specified.

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 ('Fetch one Threads post') plus the lookup key ('provider post id'), which is enough to separate it from threads_list_recent_posts at a glance. It stops short of naming the sibling it complements or contrasting single-post fetch vs. listing.

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?

'for verification' implies a use case (confirming a post exists or inspecting its content), but there is no explicit when-to-use vs. when-to-use-instead guidance and no mention of alternatives such as threads_list_recent_posts.

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