Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

run_due_posts

Publishes every queued Instagram post whose scheduled time has arrived, performing one scheduler pass so due campaign content goes live without manual intervention.

Instructions

Publish every queued post whose time has come. Same as one scheduler pass.

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": "run_due_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, open-world, non-idempotent, non-destructive), so the description's job is smaller. It still adds real value: the effect is bulk ("every" due post) and bounded to one scheduler pass, implying it does not create or reschedule anything and that a second call may pick up newly-due items. It stops short of saying what happens to posts that fail to publish.

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?

Two short sentences, with the action and its scope front-loaded and the scheduler-pass analogy as a compact mental model. Nothing is padded or repeated.

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?

With an output schema available, return values need not be explained, and the annotations carry the mutation/idempotency profile. What remains thin is failure handling for a bulk publish; otherwise the definition is complete for a no-argument trigger tool.

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 nothing for the description to disambiguate and the baseline applies. No conflicting or missing parameter information is present.

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?

"Publish every queued post whose time has come" gives a specific verb (publish) and a precise scope (all due queued posts) rather than restating the name. It does not name a sibling such as list_scheduled_posts or the individual publish_* tools, so the agent must infer the boundary itself, but the action and its breadth are unambiguous.

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?

"Same as one scheduler pass" implicitly tells the agent this is a manual trigger of the recurring job, which is useful context. There is no explicit when-to-use versus list_scheduled_posts (read-only view) or publish_image (single post), and no statement about when not to call it.

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