Get the connected Meta Threads account's profile (username, name, avatar) and account-level insights (followers, views, likes, replies, reposts, quotes).
| Name | Required | Description | Default |
|---|---|---|---|
| in_workspace | No | Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected. |
Changes observed during successful MCP inspections.
Input schema / properties / in_workspaceAdded value: +{
+ "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful context of exactly which metrics are returned, but says nothing about auth requirements, rate limits, or the absence of historical/date scoping.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One dense sentence, front-loaded with the verb and resource, with the returned field list serving as immediate clarification. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does the right thing by enumerating the returned profile fields and metrics. Combined with annotations covering safety and a fully documented single parameter, it is nearly complete; the only gap is any sense of scope/time-window for the insights.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single in_workspace parameter is fully documented in the schema, so the description carries no additional parameter burden. Baseline 3 applies since the schema does the heavy lifting and the description never references the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and a precise resource (the connected Meta Threads account's profile and account-level insights), then enumerates the exact fields returned. The 'account-level' scope implicitly distinguishes it from post-level siblings like threads_channel_post_insights, but no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer from the 'account-level' phrasing that this differs from threads_channel_post_insights or threads_channel_list_posts rather than being told.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.