Skip to main content
Glama
Sign In
threads-mcp-server

threads-mcp-server

by N-Graves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

threads_get_post_insights

Retrieve engagement metrics for a specific post: views, likes, replies, reposts, and quotes.

Instructions

Engagement on one of your posts: views, likes, replies, reposts, quotes.

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": {
      "post_id": "<post_id>"
    },
    "name": "threads_get_post_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the burden for disclosing side effects, permissions, or error conditions. It only states the data returned and implies a read-only operation via the word 'Engagement', but does not explicitly confirm safety, ownership restrictions, or failure behavior.

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?

The description is a single, concise sentence that enumerates the relevant metrics. It is not verbose or redundant, but it could be slightly more explicit about the action (e.g., 'Retrieve engagement metrics for a post').

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?

Given the simple nature of the tool (one parameter, no output schema), the description is reasonably complete for a basic retrieval. However, it does not mention the output format, potential errors, or whether the post must be owned by the caller, leaving some ambiguity.

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?

The schema provides zero description for the post_id parameter. The tool description does not explain how to identify the post or whether it must be owned by the current user. Since schema coverage is 0%, the description should compensate but does not.

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 indicates that the tool retrieves engagement metrics (views, likes, replies, reposts, quotes) for a specific post. It is distinguishable from siblings like profile retrieval or post creation, though the verb 'get' is implied rather than stated.

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 is provided on when to use this tool versus alternatives. For example, it does not explain when 'get_my_posts' would be more appropriate for listing posts, or how to obtain a post_id.

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