Skip to main content
Glama
Threads MCP

Threads MCP

by kerwilgil

List recent Threads posts

threads_list_recent_posts
Read-onlyIdempotent

Retrieve recent Threads posts to verify content and detect duplicates before publishing or reviewing account activity.

Instructions

List recent Threads posts for verification and duplicate detection.

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_list_recent_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/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 elsewhere. The description adds nothing beyond that: it does not define the time window that "recent" covers, how many posts come back, or whether results are paginated. For a feed-listing tool, the undefined recency window is a real gap.

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, front-loaded, with no filler or redundancy. It is efficient, though its brevity edges into under-specification rather than tight conciseness.

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?

An output schema exists, so return values need no explanation. However, for a listing tool the description should still establish the recency window and the meaning of limit. It is adequate for a simple read but leaves the agent guessing about scope.

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

Parameters2/5

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

Schema coverage is 0%, so the single limit parameter (default 10) is undocumented in both the schema and the description. The description never explains that limit caps the number of posts returned or how it interacts with "recent." With only one parameter this is a moderate gap, but the description does nothing to compensate.

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: "List recent Threads posts." That clearly separates it from the publish and get_post siblings, though it never names an alternative explicitly. The only weakness is that "recent" is left undefined.

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 phrase "for verification and duplicate detection" implies a context of use, so the agent knows this is a bulk-recent-read for checking duplication. There is no explicit when-not guidance, no mention of the get_post/get_profile siblings, and no stated precondition before calling.

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