View, set, or delete Instagram Ice Breakers so new chatters see up to four FAQ prompts and payloads. Use it to manage automated first-response questions and postback actions.
View, set, or delete Instagram Ice Breakers (frequently asked questions shown to new chatters).
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Action: "get", "set", or "delete". | |
| ice_breakers | No | Required if action is "set": List of up to 4 questions and payloads. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden. It does not disclose whether 'set' replaces or appends to existing Ice Breakers, whether 'delete' is destructive/irreversible, what permissions are needed, or what the response contains — significant gaps for a tool with mutating actions.
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?
A single front-loaded sentence with the verb set first and a useful parenthetical definition; no wasted words.
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?
For a two-parameter configuration tool with a fully documented schema, the description covers purpose and the resource concept adequately. However, the lack of annotations means behavior around mutation, permissions, and replacement semantics is left unaddressed.
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%, with the action enum and the 'up to 4 questions, 80 chars' constraints fully documented in the schema. The description adds no parameter detail beyond the schema, so the baseline 3 is appropriate.
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?
Uses specific verbs (View, set, delete) with a clearly named resource (Instagram Ice Breakers) and even explains what the resource is (FAQs shown to new chatters). Distinguishable from most siblings, though it doesn't explicitly contrast with the analogous manage_persistent_menu.
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 guidance on when to choose get vs set vs delete beyond restating the action names, and no prerequisites, permission requirements, or mention of an alternative tool. The agent must infer usage entirely from the action enum in the schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.