Skip to main content
Glama

Post it (organic posts)

adgpt_post_it
Destructive

Post it: publish or schedule organic posts (not ads) to your own Facebook Pages, Instagram and TikTok accounts. 1) Accounts are connected once, in the web app at https://app.adgpt.com/creative/hosted (a browser sign-in with each platform; it cannot be done here). listAccounts shows what is connected; TikTok may show as unavailable until it is approved, and an account with status reconnect_required must be reconnected in the web app. 2) What to post: a campaign creative id (campaignCreatives lists one campaign's postable images and videos) or your own media (upload_… ids from listMedia). To post your own video or photo from a link (Google Drive shared as "Anyone with the link", Dropbox, or a direct file link): call importQuote first (free: the file size and its credit cost); importMedia then spends credits by file size (charged only when the import succeeds; a few imports can run at once); poll mediaStatus every few seconds until status is ready (post its id) or failed (show its error). Your own files are deleted from our servers 7 days after their last post goes out, or 30 days after upload if never posted (never while a post using them is pending). 3) Post: buildDrafts lays several creatives out as a DRAFT posting calendar across the chosen accounts — nothing goes out until approveDrafts (review with listDrafts, adjust a draft with updatePost, or discardDrafts); or schedulePost posts one creative to one or more accounts now, or at scheduled_at. listPosts reads the calendar (from/to); updatePost, publishNow and deletePost manage single posts. A TikTok account needs the tiktok options (privacy_level and the interaction and disclosure choices) on schedulePost and buildDrafts. Actions: listAccounts, campaignCreatives, listMedia, importQuote, importMedia, mediaStatus, buildDrafts, listDrafts, approveDrafts, discardDrafts, listPosts, schedulePost, updatePost, publishNow, deletePost. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_post_it"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a mutating, non-idempotent, destructive tool. The description adds material behavior beyond that: importMedia spends credits by file size charged only on success, a few imports can run concurrently, media is deleted 7 days after last post or 30 days after upload unless a post is pending, and nothing publishes until approveDrafts. It does not detail what deletePost or discardDrafts irreversibly remove, so a small gap remains on the destructive side.

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?

Long but front-loaded and organized as a numbered workflow (connect, source media, post), with the action list rolled up at the end. The heavy parentheticals make individual sentences dense, though almost every clause carries operational information such as credit cost, polling cadence, or retention windows.

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?

For a 15-action tool with a nested free-form params object and no output schema, the description covers the end-to-end workflow, prerequisites, cost model, and lifecycle of uploaded media. The one substantive omission is per-action parameter detail, which is deliberately delegated to adgpt_capabilities rather than left unexplained.

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 only 50% and the params object is an opaque bag, so the description would need to compensate. It does convey some semantics (scheduled_at, calendar from/to on listPosts, required tiktok options such as privacy_level plus interaction and disclosure choices) but explicitly defers per-action parameters to adgpt_capabilities with the operationId, meaning an agent cannot construct params from this definition alone.

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

Purpose5/5

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

States a specific verb and resource ('publish or schedule organic posts (not ads) to your own Facebook Pages, Instagram and TikTok accounts') and explicitly excludes ads, which is the most likely reason to confuse this with a sibling tool. The scope is clear before any action list is read.

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

Usage Guidelines5/5

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

Gives explicit routing between the two posting paths: buildDrafts for a multi-creative calendar requiring approveDrafts, versus schedulePost for one creative to one or more accounts now or at scheduled_at. It also names prerequisites (accounts must be connected in the web app, reconnect_required handling, TikTok approval) and the import chain importQuote → importMedia → mediaStatus with polling guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources