Skip to main content
Glama

Generate a GEO/AEO article

generate_article

Starts generating a new SEO/GEO-optimized article via AI for a given topic and site. Counts against the account's monthly article quota, same as generating from the dashboard. Does NOT publish it — call publish_article separately once you're happy with it.

ASYNC: this returns a jobId immediately, it does NOT wait for the article. Generation typically takes 1-2 minutes (reasoning model, non-streaming) — poll get_generation_status with the returned jobId every ~15-20s until status is "ready" or "error". (Older integrations that awaited this call directly would hit their own client's default request timeout, typically 60s, long before generation finished — this is why it's async now.)

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": {
      "topic": "<topic>"
    },
    "name": "generate_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe article topic or working title
siteIdNoTarget site id (from list_sites) — determines language, tone and SEO tags used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false); the description adds the material consequences the annotations cannot: it consumes the account's monthly article quota identical to dashboard generation, returns a jobId instead of waiting, and takes 1-2 minutes. It does not state what happens on duplicate calls (e.g., whether a second call burns another quota unit), which matters given idempotentHint=false, but the async and billing disclosures are substantial.

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?

Front-loaded purpose, then a bolded ASYNC block with the polling recipe — good structure for a high-latency tool. The trailing parenthetical explaining why older integrations break is partly agent-irrelevant history, but it does justify the async contract and discourage callers from treating the call as synchronous.

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

Completeness5/5

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

With no output schema, the description carries the return contract and does so: the call yields a jobId immediately, and status is retrieved via get_generation_status. Billing impact, latency, and the follow-up publish step are all covered, which is everything an agent needs to invoke and sequence this tool correctly.

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 both parameters are already documented, including that siteId drives language, tone and SEO tags. The description adds little beyond 'for a given topic and site' — no guidance on what makes a good topic string versus a working title, despite the schema framing topic as either.

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 ('Starts generating a new SEO/GEO-optimized article via AI for a given topic and site') and immediately carves out what it does not do ('Does NOT publish it'). The distinction from publish_article is explicit, so an agent can choose between them without inspecting schemas.

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 a full workflow: call this to start, then poll get_generation_status with the returned jobId every ~15-20s until 'ready' or 'error', then call publish_article once satisfied. It names the alternative tools and the conditions that select them, leaving nothing to inference.

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