Enterprise Threads MCP Server

get_thread_insights

Retrieve specific performance metrics for any of your threads. Choose from engagement, reach, and other key metrics over a selected time period to track your content's effectiveness.

Instructions

Get performance metrics for your specific thread

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": {
      "thread_id": "<thread_id>",
      "metrics": "<metrics>"
    },
    "name": "get_thread_insights"
  }
}

Input Schema

Name	Required	Description
`period`	No	Time period for metrics
`metrics`	Yes	Metrics to retrieve
`thread_id`	Yes	ID of your thread

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.1.0Aug 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits, but it only restates the purpose. It doesn't mention read-only behavior, required permissions, or error handling (e.g., invalid thread IDs or metric names), which is a significant transparency gap.

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, focused sentence with no redundant wording, achieving maximum conciseness. It front-loads the key action and resource, making it easy to parse.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description is too sparse. It lacks details on what metrics can be requested, the meaning of period values, and the expected output format, making it incomplete for an agent to fully understand the tool's behavior.

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?

The schema already describes all three parameters with clear descriptions, so the baseline is 3. The description adds nothing about parameter semantics, but the schema covers the basics (thread_id, metrics array, period enum), making the additional description unnecessary.

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 clearly states the tool retrieves performance metrics for a specific thread, using the verb 'get' and specifying the resource. However, it doesn't distinguish from other analytics tools like get_my_insights or get_enhanced_insights, so it loses a point for lack of sibling differentiation.

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?

The description provides no context about when to use this tool instead of alternatives, such as get_my_insights for broader metrics or get_thread_replies for replies. It merely states the function, leaving the agent without guidance on selection criteria.

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

Deploy Server