Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

list_dm_automations

List DM automation rules for Instagram and Facebook with funnel stats, monthly contact usage versus plan cap, and accounts Meta is rate-limiting.

Instructions

List the DM automation rules on your Instagram/Facebook accounts, with per-rule funnel stats (reached → opted in → clicked, plus captured emails), this month's contact usage vs plan cap, and any accounts Meta is rate-limiting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dm_automations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does valuable work by revealing that the response includes derived statistics (reached → opted in → clicked), plan-cap consumption, and accounts currently rate-limited by Meta, which is real behavioral context beyond a bare list. It remains silent on auth requirements, pagination, result ordering, and whether the call itself is subject to the rate limits it reports.

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?

One front-loaded sentence opens with the verb and resource, then appends the payload contents in a scannable chain. It is dense but every clause (funnel stats, contact usage, rate-limited accounts) adds information an agent cannot get elsewhere; the parenthetical funnel detail is slightly verbose but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, no annotations, and no parameters, so the description is the only place return content can be explained — and it does so thoroughly, covering both rule-level metrics and account-level usage and rate-limit signals. It stops short of describing response shape or what an empty result looks like, which an agent would still need to discover.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless tool is 4. Nothing in the description misdescribes inputs, and the scope ("your Instagram/Facebook accounts") makes clear the account set is implicit rather than a filter argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the DM automation rules") scoped to "your Instagram/Facebook accounts," then enumerates exactly what each listing carries: funnel stats, monthly contact usage vs plan cap, and Meta rate-limit status. This clearly distinguishes the read operation from the create/update/delete_dm_automation siblings without the agent needing to open a schema.

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?

Usage is implied by the verb "List" — an agent reading this knows it is the read path for DM automation rules. However, there is no explicit when-to-use statement, no exclusions, and no pointer to alternatives such as get_account_analytics for broader metrics or list_accounts for account-level detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.