Skip to main content
Glama
omnipost-social-engine

omnipost-social-engine

by 1nc0gn30

omni_export_campaign

Exports a multi-post social campaign to Buffer/Hootsuite CSV, JSON bundle, Markdown calendar, or plain text for scheduling and sharing.

Instructions

Export a multi-post social campaign into Buffer/Hootsuite CSV, JSON bundle, Markdown calendar, or plain text.

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": {
      "campaign": "<campaign>"
    },
    "name": "omni_export_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport format: 'json', 'csv', 'markdown' / 'md', 'txt' / 'raw'.json
presetNoCSV preset: 'buffer', 'hootsuite', 'typefully', 'generic'.buffer
campaignYesCampaign dictionary, list of posts, or raw text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and leaves the most important question unanswered: does it write a file to disk or return the serialized content in the response? It also omits whether the tool is side-effect free, whether CSV presets require an external service, and any error behavior for malformed campaign input.

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?

A single front-loaded sentence: verb, resource, then the format list. No preamble, no redundant restatement of the tool name, and every clause contributes the list of supported export targets.

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 schema is small and fully described, so parameter semantics are covered, but there is no output schema and the description never explains what the caller receives back. For an export tool whose entire value is the produced artifact, that is a meaningful gap even at low complexity.

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 100%, so the enum values for format and preset are already documented in the input schema, making 3 the baseline. The description does slightly reinforce the mapping by naming Buffer/Hootsuite alongside CSV and by confirming Markdown is rendered as a calendar, but adds no new syntax or constraint detail.

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 gives a specific verb and resource ('Export a multi-post social campaign') and enumerates the concrete output targets (Buffer/Hootsuite CSV, JSON bundle, Markdown calendar, plain text). This distinguishes it clearly from siblings like omni_format_post or omni_generate_campaign_links, though it never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance, no prerequisites (e.g., does Buffer/Hootsuite export require credentials?), and no pointer to a sibling for related tasks. The agent must infer that this is the tool for serializing a finished campaign, which is implied but never stated.

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