Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

reschedule_post

Move a pending, failed, or cancelled Instagram post to a new publish time and re-arm it for scheduled delivery.

Instructions

Move a pending/failed/cancelled post to a new time (re-arms it).

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": {
      "post_id": "<post_id>",
      "publish_at": "<publish_at>"
    },
    "name": "reschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
publish_atYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a mutation that is not destructive and not open-world; the description adds meaningful behavior with '(re-arms it)', telling the agent the post becomes active again. It says nothing about permissions, side effects on prior failure state, or what happens to the old schedule.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the action and the eligibility constraint, with the parenthetical behavior note last. No filler.

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

Completeness3/5

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

The output schema means return values need not be explained, and the annotations cover the safety profile. However, for a mutation with two undocumented required parameters, the definition leaves format and permission questions unanswered.

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%, yet the description says nothing about post_id or publish_at — not the accepted time format, timezone handling, or whether past times are rejected. With two required params fully undocumented in the schema, the description should compensate and does not.

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 and resource ('Move a ... post to a new time') and clarifies scope by listing the eligible states (pending/failed/cancelled). An agent can tell this re-time operation apart from create-style siblings, though no sibling is named explicitly.

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?

The eligible-status list implies a precondition for use, but there is no explicit when-not guidance, no mention of what to do for posts in other states, and no routing to alternatives like schedule_post or cancel_scheduled_post.

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