Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

threads_get_user_insights

Retrieve account-level Threads insights for views, likes, replies, reposts, quotes, clicks, followers, and follower demographics to analyze performance and audience trends over a date range.

Instructions

Get account-level Threads insights (views, likes, replies, reposts, quotes, clicks, followers, follower demographics).

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": {
      "metric": "<metric>"
    },
    "name": "threads_get_user_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoStart date (Unix timestamp)
untilNoEnd date (Unix timestamp)
metricYesComma-separated metrics: views,likes,replies,reposts,quotes,followers_count,follower_demographics
breakdownNoRequired when requesting follower_demographics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.2
    • addedInput schema / properties / breakdown
      Added value: +{
+  "description": "Required when requesting follower_demographics",
+  "enum": [
+    "country",
+    "city",
+    "age",
+    "gender"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / metric / description
      Previous value: -"Comma-separated metrics: views,likes,replies,reposts,quotes,clicks,followers_count,follower_demographics"New value: +"Comma-separated metrics: views,likes,replies,reposts,quotes,followers_count,follower_demographics"
  2. First observedv2.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state that this is a read-only operation, what permissions or account type are needed, whether the date range has limits, or roughly what the response contains — only the metric names overlap with what the schema already lists.

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?

A single dense sentence with the resource and its scope front-loaded and zero filler. The only weakness is that the parenthetical metric list largely duplicates the schema's metric description.

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?

With no output schema and no annotations, the description should explain the shape of the returned insights and any permission or date-range constraints; it only implies the returned fields via the metric list. Adequate to pick the tool, thin for invoking it correctly in edge cases.

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 coverage is 100%, so since/until/metric/breakdown are all documented in the schema, including the enum for breakdown and the 'required when requesting follower_demographics' rule. The description adds nothing beyond restating the metric names, so the 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?

States a specific verb ('Get') and resource ('account-level Threads insights') and enumerates the metric families returned. The 'account-level' qualifier implicitly separates it from the post-level sibling threads_get_post_insights, though it never names that sibling explicitly.

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?

Scope ('account-level') and the metric list hint at when this applies, but there is no explicit when-to-use statement, no mention of the alternative (threads_get_post_insights, ig_get_account_insights), and no prerequisites such as required permissions or date-range constraints.

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