Skip to main content
Glama

Social publishing

adgpt_social
Destructive

Connect your own Facebook ad account, check connections, and publish to TikTok from an account you already connected in the web app: campaign/ad-group reads, targeting taxonomy, and create-ads. Actions: connectAccount, checkConnection, facebookExchangeToken, tiktokRegions, tiktokLanguages, tiktokCampaigns, tiktokAdGroups, tiktokCreateAds. 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_social"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description never says what is destructive or whether create-ads is reversible. It does add genuine context the annotations lack: an OAuth-style token exchange (facebookExchangeToken) and the requirement that the TikTok account be pre-connected in the web app. Rate limits, error behavior, and mutation side effects remain undisclosed.

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

Conciseness3/5

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

The opening sentence is a run-on that crams three goals plus a colon-list of capabilities into one clause, which hurts front-loading. The explicit action list duplicates the input schema's enum verbatim and consumes roughly a third of the text without adding information. The final sentence about adgpt_capabilities is the highest-value line and is placed last.

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?

For an eight-action dispatcher with no output schema, nested free-form params, and a destructive annotation, the description is thin on what each action returns and how errors surface. Delegating parameter discovery to adgpt_capabilities mitigates this substantially. It still leaves the destructive flag and the connectAccount vs facebookExchangeToken distinction 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 50%: the action enum is fully specified in the schema, but params is a free-form object with no per-action shape. The description compensates partly by telling the agent to call adgpt_capabilities with the operationId to discover each action's parameters, which is the key procedural fact. It adds no semantic meaning about any individual parameter itself.

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 concrete verbs and resources: connect a Facebook ad account, check connections, publish to TikTok, read campaigns/ad groups, and create ads. It enumerates the eight actionIds, so an agent knows the tool's surface. It stops short of differentiating from siblings like adgpt_account or adgpt_campaigns, which cover overlapping territory.

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?

There is partial situational guidance: TikTok publishing only works from an account already connected in the web app, implying connectAccount/facebookExchangeToken are prerequisites. It also routes the agent to adgpt_capabilities for per-action parameters. However, there is no guidance on when to pick this tool over adgpt_account, adgpt_campaigns, or adgpt_go_live.

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