Skip to main content
Glama

Get Threads Posts

threads_get_posts
Read-only

Retrieve your Threads posts with optional date range and pagination filters.

Instructions

Lists the authenticated user's Threads posts.

Args:

  • threads_user_id (string): Threads user ID (from threads_get_profile)

  • limit (number): Max results (1–100, default 20)

  • since (string, optional): Start date YYYY-MM-DD

  • until (string, optional): End date YYYY-MM-DD

  • after (string, optional): Pagination cursor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threads_user_idYesThreads user ID
limitNo
sinceNo
untilNo
afterNo
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior2/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds no extra behavioral context beyond 'Lists...', missing details like rate limits, ordering, or data freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise paragraph with clear argument list. Every sentence adds value, no filler.

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?

All parameters are explained. Lacks details on return format, pagination behavior, or ordering, but overall adequate for a list tool without output schema.

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 description coverage is low (33%). The description adds meaningful context for each param: provenance for threads_user_id, range/default for limit, date format for since/until, and purpose for after (pagination cursor).

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?

The description clearly states 'Lists the authenticated user's Threads posts', using a specific verb and resource. It distinguishes from sibling tools like threads_get_post (single post) and threads_get_replies (replies).

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?

The description provides parameter details but no explicit when-to-use vs alternatives. It implies usage for listing all posts but lacks guidance on when to filter or paginate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server