Skip to main content
Glama

Draft marketing content

gtm_generate_content
Idempotent

Generate and persist a new GTM content draft for the authenticated user. Repeating the same call within 10 minutes returns the same draft.

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

Input Schema

NameRequiredDescriptionDefault
countNoPosts: how many separate drafts (1-20, each its own draft; one call makes up to 6 and says how many are left to ask for). Threads and series: how many parts (1-20).
channelNoDelivery channel. One of: x|linkedin|facebook|instagram|youtube|email|webx
languageNoOptional language
appSourceNoWhich business the draft is about: custom (your saved business, the default) | a build session id
_confirmedNoSet to true only after the user has explicitly approved this exact write or credit-spending action.
campaignIdNoOptional campaign id
contentClassNoContent class. One of: product_led|brand_led|domain_led|offer_ledproduct_led
operatorPromptNoOptional operator instruction for the generator
deliverableTypeNoDeliverable type. One of: post|thread|launch_pack|bio|promo_campaign|educational_series|landing_copy|visual_brief|seo_blog_post|seo_landing_page|llms_txtpost

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of variants to generate (1-20)"New value: +"Posts: how many separate drafts (1-20, each its own draft; one call makes up to 6 and says how many are left to ask for). Threads and series: how many parts (1-20)."
  2. Changed2 schema fields changed
    • removedInput schema / properties / appSource / default
      Removed value: -"promptui"
    • changedInput schema / properties / appSource / description
      Previous value: -"promptui | custom session id"New value: +"Which business the draft is about: custom (your saved business, the default) | a build session id"
  3. Changed1 schema field changed
    • changedInput schema / properties / deliverableType / description
      Previous value: -"Deliverable type. One of: post|thread|launch_pack|bio|promo_campaign|educational_series|landing_copy|cinematic_video_teaser|visual_brief|seo_blog_post|seo_landing_page|llms_txt"New value: +"Deliverable type. One of: post|thread|launch_pack|bio|promo_campaign|educational_series|landing_copy|visual_brief|seo_blog_post|seo_landing_page|llms_txt"
  4. 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"
      +}
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=true; the description earns credit for making idempotency concrete ("same call within 10 minutes returns the same draft"). However it omits significant behavioral facts for a mutating, possibly credit-spending tool: whether credits are consumed, where the draft is persisted, and whether drafts are editable or deletable afterward.

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, zero filler, with the identity of the tool and the idempotency window both front-loaded. Every sentence earns its place.

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 a 9-parameter generation tool with no output schema, the description should say what comes back (draft id, URL, or content body) and whether credits are spent. It covers persistence and deduplication but leaves the return shape and cost model unstated, which is a meaningful gap given the absence of an output schema.

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 description coverage is 100%, so every parameter including the deliverableType/channel/contentClass enumerations and the count semantics is already documented in the schema. The description adds no meaning beyond it, so the 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?

States a concrete verb pair and resource: "Generate and persist a new GTM content draft for the authenticated user." An agent can tell this creates a draft rather than listing (gtm_list_content) or publishing (gtm_publish_content), though the description never names those siblings 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?

No guidance on when to choose this over gtm_list_content or gtm_publish_content, and no mention of prerequisites such as user approval or credit expenditure that the schema's _confirmed flag implies. The only usage-adjacent statement is a retry/dedup note, which is behavioral rather than when-to-use 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