Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_post

Retrieve a public Threads post by username and post code, returning text, URL, preview image, and author details.

Instructions

Retrieve a public Threads post. Returns one public Threads post by username (with or without a leading @) and the post code from its URL. The response has the post text, canonical URL, preview image URL, and the author's id, name and username. Replies and logged-in fields are not included. An unavailable post returns 404.

Input Schema

NameRequiredDescriptionDefault
codeYesThreads post code
usernameYesThreads username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the returned fields (text, canonical URL, preview image URL, author id/name/username), what is excluded (replies and logged-in fields), and the error behavior (404 for unavailable posts). It does not state rate limits or auth requirements, so it is not exhaustive, but it is a solid behavioral picture.

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?

Four sentences, front-loaded with the core action and identifier requirements, then return fields, then exclusions and error behavior. Every sentence carries information; only the first two sentences overlap slightly in restating the same retrieval.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates fully: it enumerates the response fields, notes the omitted fields, and documents the 404 failure mode. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema's terse 'Threads username'/'Threads post code': it clarifies that the username may be given with or without a leading '@' and that the code is taken from the post URL. That is genuine disambiguation of both parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Retrieve) and a precisely scoped resource (one public Threads post, identified by username + post code). It is immediately distinguishable from siblings like threads_profile_posts, threads_search, and threads_post_replies, which operate on collections or replies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context clear: you need a username and the post code taken from the post's URL, which tells the agent how to obtain the required identifiers. It does not, however, name alternatives (e.g. threads_search for finding a post when the code is unknown) or state exclusions, so it stops short of explicit when/when-not guidance.

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