Skip to main content
Glama

generate_content

Generates marketing content for multiple channels from a product, category, or brand source, previewing first unless approval is confirmed.

Instructions

Preview by default. Set confirm to request approval for this exact body.

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": {
      "body": "<body>"
    },
    "name": "generate_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNo
run_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: calls are non-committing previews unless confirm is set, at which point approval is requested for that exact body. That is meaningful mutation-safety context. However, it says nothing about cost implications, what a preview returns, whether approval is synchronous, or whether approved content is actually published or merely generated.

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?

Two short sentences, front-loaded with the default behavior, with no filler wording. The terseness is efficient structurally, though it borders on under-specification given the tool's complexity.

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?

For a tool with a large nested request object, 0% schema coverage, no annotations, and no output schema, the definition is far too thin. An agent still lacks what the tool produces, how channels and parameters affect output, what run_label does, and what a preview versus approved call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate, and it only partially explains confirm (approval for the exact submitted body). The run_label parameter is entirely undocumented, and body — a deeply nested object requiring source.subject.type, parameters, and 1-10 channels — receives no explanation at all in either schema or description.

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

Purpose2/5

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

The description never states what is generated: it only describes invocation mode ("Preview by default. Set confirm to request approval for this exact body."). What the tool produces, and for which resource, is only inferable from the tool name and the nested schema (channels, source subject). An agent cannot distinguish this from siblings like enrich_title or research_market based on the text alone.

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 related tools such as estimate_cost or list_parameters, and no stated prerequisites for generating content. The preview/confirm sentence explains how a call behaves once made, not when this tool should be selected over alternatives.

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