Skip to main content
Glama

Publish a post to a connected channel

gtm_publish_content

Publish one GTM content item to a connected social platform.

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": {
      "contentId": "<contentId>"
    },
    "name": "gtm_publish_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNoOptional LinkedIn/Facebook page target id
igUserIdNoOptional Instagram user id target
platformNoOptional platform override: x|linkedin|facebook|instagram|tiktok|threads
contentIdYesGTM content id to publish
_confirmedNoSet to true only after the user has explicitly approved this exact write or credit-spending action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / description
      Previous value: -"Optional platform override: x|linkedin|facebook|instagram|tiktok"New value: +"Optional platform override: x|linkedin|facebook|instagram|tiktok|threads"
  2. Changed1 schema field changed
    • addedInput schema / properties / _confirmed
      Added value: +{
      +  "default": false,
      +  "description": "Set to true only after the user has explicitly approved this exact write or credit-spending action.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world operation, so the safety profile is known. The description adds nothing further: it does not warn that publishing is externally visible and irreversible-ish, that non-idempotent calls can duplicate a post, or that a user-confirmation gate applies. For an outward-facing write action, that is a real gap.

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?

A single front-loaded sentence with zero filler and no ambiguity. It is efficient, though the brevity borders on under-specification for a five-parameter external write tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutating, open-world tool with five parameters, a confirmation gate, no output schema, and no annotations explaining return behavior. The description says nothing about what is returned (post id? URL?), failure modes, or the required confirmation step, which is inadequate context for the tool's 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 all five parameters including the platform enum values and the _confirmed approval gate are documented in the schema itself. The description adds no extra meaning about target selection precedence (pageId vs igUserId vs platform) or what happens when no platform is specified, so baseline 3 applies.

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 one GTM content item to a connected social platform' states a specific verb and resource, and the singular 'one ... item' plus 'connected' scope it clearly apart from gtm_generate_content and gtm_list_content. It stops short of explicitly naming those siblings or the multi-platform targets, so it is clear but not maximally differentiated.

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 guidance, no mention of prerequisites (an already-connected channel/account), and no routing to alternatives such as gtm_generate_content for creating the item first. The confirmation requirement implied by _confirmed is never surfaced in prose, leaving the agent to infer the workflow entirely from the schema.

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