Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_my_threads

Fetch your own Threads posts with optional filters for limit, date range, and fields. Use this tool to access your posting history for analytics or content management.

Instructions

Get your own threads/posts

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": "get_my_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of threads to retrieve
sinceNoISO 8601 date for filtering
untilNoISO 8601 date for filtering
fieldsNoThread fields to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It doesn't disclose whether this is a read-only operation, the default field set, pagination via 'limit', or date filtering semantics. It only states a basic retrieval operation.

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 sentence, immediately front-loaded with the action and resource. No filler words.

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?

The tool is simple with four optional params and no output schema, so the description should provide more context about the return format or when to use it. It lacks guidance on the default behavior (e.g., all threads vs recent) and does not distinguish from 'search_my_threads'.

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% for all four parameters (limit, since, until, fields), so the schema already documents their meaning. The description adds no parameter semantics beyond the name 'get_my_threads'.

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?

The description states a clear verb ('Get') and resource ('your own threads/posts'), establishing what the tool retrieves. However, it doesn't differentiate from sibling tools like 'search_my_threads' or 'get_thread_replies', so it's not fully distinct.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., search_my_threads for filtering, get_thread_replies for replies). The description is purely functional and lacks any contextual use case.

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