Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

threads_profile_media

Fetch public media posts from a Threads profile, returning first-page image and video URLs, carousel attachments, post metadata, and a pagination limit flag.

Instructions

Retrieve public media posts from a Threads profile. Returns the first public page shown on a profile's Media tab. Items include image and video URLs, including carousel attachments, plus post and topic metadata. The logged-out page exposes no continuation cursor or media-type filter; pagination_limited reports when additional results are gated by login or lack a supported cursor.

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": {
      "username": "<username>"
    },
    "name": "threads_profile_media"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Threads username

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.13Oct 20, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that only the first public page is returned, that no continuation cursor exists, and that `pagination_limited` flags login-gated results. This is exactly the kind of behavioral context an agent needs; only auth/permission specifics are absent.

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?

Front-loaded with the core action, then return contents, then the pagination caveat. Four sentences, all earning their place, though the pagination sentence is dense enough to require a second read.

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

Completeness4/5

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

With no output schema or annotations, the description compensates by enumerating return contents (image/video URLs, carousel attachments, post and topic metadata) and the pagination limitation. Little is missing for correct invocation, though error/empty-profile behavior is not addressed.

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?

One parameter with 100% schema description coverage, so the schema already documents `username`. The description adds nothing about the parameter beyond what the schema states, which is the expected baseline for a fully-covered single-param schema.

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 ('Retrieve public media posts from a Threads profile') and scopes it to the Media tab so it is distinguishable from text-post siblings. It never names threads_profile_posts or threads_profile_replies explicitly, so sibling differentiation is implicit rather than explicit.

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 implied by the 'media' scope and the mention that the logged-out page exposes no media-type filter, but there is no explicit when-to-use/when-not guidance or named alternative to route the agent away from other profile tools.

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

Deploy Server