list_broadcastsRetrieve your account's broadcasts, newest first, to review sent Instagram broadcast campaigns. Requires a Pro plan with BROADCAST access.
List the account's broadcasts (newest first). Requires the Pro plan (BROADCAST).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true, and the description adds two pieces of genuine behavioral context beyond that: the result ordering ('newest first') and an entitlement precondition (Pro plan / BROADCAST). It stops short of describing pagination or result limits, which would be needed for a 5.
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?
Two short sentences, zero waste, with the core action and ordering front-loaded and the plan requirement appended where it belongs.
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 zero-parameter read tool with no output schema, the description covers what it returns conceptually (a list of broadcasts), the ordering, and the plan gate. Only pagination/volume behavior is unaddressed, a minor gap given the tool's simplicity.
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 tool takes zero parameters, so the baseline of 4 applies; there is no parameter surface for the description to clarify or omit.
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 and resource ('List the account's broadcasts'), which clearly separates it from the mutating siblings create_broadcast and send_broadcast. It does not explicitly name or differentiate against any sibling, so it falls short of the 5 benchmark.
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?
The description implies the obvious use case (enumerate existing broadcasts) and adds an eligibility gate ('Requires the Pro plan (BROADCAST)'), but it never states when to prefer this over list_tags/list_automations or how it relates to create/send_broadcast. Usage is inferable but not spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.