Skip to main content
Glama

threads_channel_list_posts

Read-onlyIdempotent

List posts published by the connected Meta Threads account. Returns id, text, permalink, media_type and timestamp. Paginate with the returned after cursor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "threads_channel_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor from a previous call's `after`.
limitNoPage size, 1-100. Default 25.
sinceNoISO date (YYYY-MM-DD) lower bound.
untilNoISO date (YYYY-MM-DD) upper bound.
account_idNoWhich connected Threads account to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected Threads account to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the result shape and the pagination mechanism (returned `after` cursor), which is useful, but says nothing about result caps, rate limits, or that only the connected account's own posts appear.

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?

Three short sentences, front-loaded with purpose, then return shape, then pagination. No filler; only mild redundancy in restating the `after` cursor that the schema already documents.

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, stating the returned fields (id, text, permalink, media_type, timestamp) fills a real gap, and pagination is addressed. Multi-account behavior and parameter semantics are already fully documented in the schema, so little is missing for a simple read-only list 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?

Schema description coverage is 100%, including the account_id multi-account refusal rule and the limit/since/until semantics, so the schema does the heavy lifting. The description only reinforces the `after` cursor's provenance and adds no meaning beyond the schema; 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?

Specific verb+resource with scope: "List posts published by the connected Meta Threads account," plus the returned fields. It does not distinguish itself from plausible siblings (e.g., search_threads for filtered search, posts_publish for writes), so it stops short of a 5.

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 "published by the connected account" and by the pagination note, but there is no explicit when-to-use or when-not guidance and no named alternative for cases like searching or fetching a single post.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.