Skip to main content
Glama

resubscribe_webhooks

Idempotent

Re-subscribe the Instagram account to the comment and message feeds that automations run on. Instagram only delivers a comment or DM to reeldrop while that subscription exists; it is made when the account is connected, and can be lost (an account connected before it was automatic, or Instagram dropping it).

Use it when comments or DMs stopped triggering automations although the connection is healthy (get_instagram_profile says connection_ok), no automation reports stalled, and get_automation_logs shows nothing new for comments that should have matched. It is safe to repeat — subscribing twice changes nothing — and sends nothing to anyone. If the connection itself has expired, reconnecting in reeldrop is the fix, not this.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>"
    },
    "name": "resubscribe_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: it discloses that the tool sends nothing to anyone, that the subscription is created at connect time and can be silently lost, and that repeating the call is harmless. The idempotency point overlaps with idempotentHint=true, but the non-effect and subscription-lifecycle details are genuinely additive.

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?

Front-loaded with the action, then the precondition, then the exclusion — a sensible order. The parenthetical about how the subscription is lost is slightly wordy but carries real diagnostic value, so little needs cutting.

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?

Output schema exists, so return values need no explanation, and the diagnostic preconditions are thoroughly covered. The one shortfall is the total silence on the two required parameters, which is the only thing an agent could get wrong when calling it.

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

Parameters2/5

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

Schema description coverage is 0%, so both required parameters (workspace_id, ig_account_id) fall entirely to the description, and it never mentions them. The prose implies 'the Instagram account' but gives no guidance on which account ID to pass or how workspace scoping interacts with the subscription.

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: "Re-subscribe the Instagram account to the comment and message feeds that automations run on." It also explains what a subscription is and how it is created/lost, which is enough for an agent to distinguish this from sibling tools like get_automation_logs or get_instagram_profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit diagnostic recipe: use it only when comments or DMs stopped triggering automations while get_instagram_profile reports connection_ok, no automation is `stalled`, and get_automation_logs shows nothing new. It also names the exclusion — if the connection has expired, reconnecting is the fix, not this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources