insta-pilot

ig_comments_toggle

Enable or disable comments on a specific Instagram post by media ID, with optional account selection and dry-run preview.

Instructions

Activa o desactiva los comentarios de una publicación.

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": {
      "media_id": "<media_id>",
      "enabled": "<enabled>"
    },
    "name": "ig_comments_toggle"
  }
}

Input Schema

Name	Required	Description
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)
`dry_run`	No	true = solo muestra lo que haría, sin ejecutar
`enabled`	Yes
`media_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation-but-not-destructive profile is already known. The description adds nothing beyond confirming it toggles a setting — no mention of permissions required, whether the change is reversible, or the effect on existing comments.

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?

A single efficient sentence with the action front-loaded. It is not bloated, though it is sparse enough that conciseness shades into under-specification.

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

Completeness2/5

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

For a mutation tool with no output schema, two undocumented required parameters, and no annotations covering permissions or side effects, the description does far too little. An agent lacks the information needed to invoke this confidently.

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 coverage is only 50%: media_id and enabled are undocumented. The description implies 'publicación' maps to media_id and 'activar/desactivar' to enabled, but gives no format, type, or value guidance to compensate for the gap.

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

Purpose4/5

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

States a specific verb (activa/desactiva) and resource (comentarios de una publicación), so the agent knows exactly what operation occurs. It doesn't explicitly differentiate from siblings like ig_comment_hide or ig_comment_delete, which are also comment-mutating tools, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no guidance about when to use this versus ig_comment_hide, ig_comment_delete, or ig_comments, nor any mention of prerequisites or account context. The agent must infer usage purely from the name.

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