Re-enable notifications for a specified Instagram direct message thread by providing its thread ID, so you can resume receiving alerts for that conversation.
Unmute notifications for a thread.
Args: thread_id: ID of the thread to unmute.
| Name | Required | Description | Default |
|---|---|---|---|
| thread_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It identifies the state change but does not disclose permissions, reversibility, side effects, or what happens if the thread is not currently muted.
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?
The description is extremely short and front-loaded. Every sentence is useful, and there is no filler.
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?
An output schema exists, so return values need not be described. However, with no annotations, the description should provide more behavioral context for a state-changing operation; it remains minimally viable for invocation but thin on safety and usage details.
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?
The single parameter is briefly explained as 'ID of the thread to unmute.' With 0% schema description coverage, this is the only documentation, but it adds little beyond the parameter name and does not specify format or examples.
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?
The description states a specific verb and resource: 'Unmute notifications for a thread.' It is immediately distinguishable from the sibling mute_thread and other messaging tools.
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?
No when-to-use guidance, prerequisites, or alternatives are given. The agent can infer that the tool reverses mute_thread, but the description itself provides no explicit routing or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.