Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

cancel_scheduled_post

Cancels a pending or failed scheduled Instagram post by post ID and moves a pending studio asset back to approved status.

Instructions

Cancel a pending or failed scheduled post (a pending studio asset goes back to approved).

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>"
    },
    "name": "cancel_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds real behavioral detail beyond them: a pending studio asset transitions back to 'approved'. It does not disclose whether the cancellation is reversible or what happens to a failed post's data.

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 front-loaded sentence with the key side effect in a compact parenthetical. No filler, no redundant restatement of the tool name.

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?

An output schema exists, so return values need not be described, and the mutation's visible effect is stated. Still missing for a mutation tool: permission requirements, failure behavior on an ineligible id, and whether the action can be undone.

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

Parameters3/5

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

Schema coverage is 0%, so the single post_id parameter is undocumented in structured data. The description partially compensates by tying eligibility to the referenced post (it must be pending or failed), but it never says how to obtain the id or what format it takes.

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?

The description uses a precise verb+resource pair ('Cancel a pending or failed scheduled post') and narrows the eligible state to pending or failed. It clearly distinguishes itself from schedule_post and reschedule_post by action, though it never names a sibling explicitly, which keeps it from 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 Guidelines3/5

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

Usage is implied by the state constraint: only pending or failed posts qualify, so an agent knows when the call is valid. It never says what to do instead for an already-published post (e.g. delete vs reschedule) or what error surfaces on an ineligible id.

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